Triple
T25510872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susy Hendrix |
E639373
|
entity |
| Predicate | workPremieredIn |
P61113
|
FINISHED |
| Object | Broadway |
—
|
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: Broadway | Statement: [Susy Hendrix, workPremieredIn, Broadway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPremieredIn Context triple: [Susy Hendrix, workPremieredIn, Broadway]
-
A.
premieredInWorkPremiereYear
Indicates the year in which a work (such as a performance, film, or composition) had its first public premiere.
-
B.
premieredWith
Indicates that one entity made its first public debut or initial showing together with another entity, at the same time or in the same event.
-
C.
sectionPremieredIn
Indicates that a specific section or part of a work first premiered or was initially presented in a particular event, venue, or context.
-
D.
premieredIn
chosen
Indicates that a creative work first publicly debuted or was initially presented in a particular place, event, or context.
-
E.
premieredInProduction
Indicates that a work (such as a play, film, or performance) had its first public showing or debut in a specific production.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 2:49 p.m.