Triple
T32718955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Passing Show of 1916 |
E836611
|
entity |
| Predicate | firstPerformanceState |
P205143
|
FINISHED |
| Object | New York |
E550
|
NE 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: New York | Statement: [The Passing Show of 1916, firstPerformanceState, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceState Context triple: [The Passing Show of 1916, firstPerformanceState, New York]
-
A.
firstPerformanceStatus
Indicates the status or outcome of an entity’s initial or debut performance.
-
B.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
-
C.
firstPerformanceApproximate
Indicates that the timing of the first performance of something is known only approximately rather than as an exact date.
-
D.
firstPerformedAs
Indicates the initial occasion or context in which an entity (such as a work, role, or piece) was performed by a particular performer or group.
-
E.
firstPerformanceCurrentName
Indicates the earliest performance or appearance at which an entity was presented under its current name.
- F. None of above. chosen
Provenance (5 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34a79588b08190ad48f1468c0f9835 |
completed | June 19, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:11 a.m.