Triple
T31418330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Reyes |
E801460
|
entity |
| Predicate | settingOfWorkFeatures |
P33122
|
FINISHED |
| Object | Hell's Kitchen, Manhattan |
—
|
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: Hell's Kitchen, Manhattan | Statement: [Miss Reyes, settingOfWorkFeatures, Hell's Kitchen, Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfWorkFeatures Context triple: [Miss Reyes, settingOfWorkFeatures, Hell's Kitchen, Manhattan]
-
A.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
B.
featuresWorkType
Indicates that an entity includes, supports, or is characterized by a particular type or category of work.
-
C.
settingOfWorks
chosen
Indicates that a place or environment serves as the primary setting where the events or narratives of one or more works take place.
-
D.
worksOnFeature
Indicates that an entity is actively involved in developing, implementing, or contributing to a particular feature.
-
E.
workPrimaryFeature
Indicates that the referenced work serves as the main or most prominent feature in a given context (such as a release, event, or collection).
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 30, 2026, 8:45 p.m.