Triple
T12105182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pippin |
E288282
|
entity |
| Predicate | 2013RevivalOpeningDate |
P103305
|
FINISHED |
| Object | 2013-04-25 |
—
|
LITERAL 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: 2013-04-25 | Statement: [Pippin, 2013RevivalOpeningDate, 2013-04-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2013RevivalOpeningDate Context triple: [Pippin, 2013RevivalOpeningDate, 2013-04-25]
-
A.
2009RevivalOpeningDate
Indicates the calendar date on which the 2009 revival production officially began performances or opened.
-
B.
revivalYear
Indicates the year in which something (such as a work, practice, or institution) was brought back into active use or renewed after a period of decline or inactivity.
-
C.
revivalVersionChartedOn
Indicates that a particular revival version of a work is recorded as having appeared on a specific chart.
-
D.
revivalAiredOnChannel
Indicates that a revival of a show or series was broadcast on a specific television channel.
-
E.
2009RevivalClosingDate
Indicates the date on which the 2009 revival of something (e.g., a show, event, or program) officially ended or closed.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d916481a008190ae66677b9e6dd961 |
completed | April 10, 2026, 3:24 p.m. |
Created at: April 8, 2026, 9:48 p.m.