Triple
T23909595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Show Business |
E601300
|
entity |
| Predicate | performerLocation |
P154332
|
FINISHED |
| Object | New York City |
—
|
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: New York City | Statement: [Show Business, performerLocation, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerLocation Context triple: [Show Business, performerLocation, New York City]
-
A.
performerPosition
Indicates the spatial or role-based placement of a performer relative to a performance context or other participants.
-
B.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
C.
performerOrigin
Indicates that a performer originates from, or is associated with, a particular place or region.
-
D.
hasPerformerResidence
Indicates that a performer is associated with a particular place as their residence.
-
E.
performerInShow
Indicates that an entity participates as a performer in a particular show or performance.
- F. None of above. chosen
Provenance (4 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce93a20c8190b1c8170d955c8d96 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:38 p.m.