Triple
T26703331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wardell Pomeroy in Kinsey |
E673218
|
entity |
| Predicate | fieldOfWorkInWork |
P3
|
FINISHED |
| Object | human sexuality research |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: human sexuality research | Statement: [Wardell Pomeroy in Kinsey, fieldOfWorkInWork, human sexuality research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfWorkInWork Context triple: [Wardell Pomeroy in Kinsey, fieldOfWorkInWork, human sexuality research]
-
A.
fieldOfWork
chosen
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
B.
basisOfWork
Indicates that one entity serves as the foundational source, reference, or inspiration upon which another work is created or derived.
-
C.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
D.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
E.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 3:32 a.m.