Triple
T26703330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wardell Pomeroy in Kinsey |
E673218
|
entity |
| Predicate | worksForInWork |
P5820
|
FINISHED |
| Object | Alfred Kinsey |
—
|
NE NERFINISHED |
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: Alfred Kinsey | Statement: [Wardell Pomeroy in Kinsey, worksForInWork, Alfred Kinsey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksForInWork Context triple: [Wardell Pomeroy in Kinsey, worksForInWork, Alfred Kinsey]
-
A.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
B.
worksFor
chosen
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
C.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
D.
works in
Indicates that one entity performs their job or professional activities within the organization, location, or context represented by another entity.
-
E.
workWithin
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by 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_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 3:32 a.m.