Triple
T35181609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It's Only a Play |
E1015864
|
entity |
| Predicate | 2014RevivalCity |
P174170
|
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: [It's Only a Play, 2014RevivalCity, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2014RevivalCity Context triple: [It's Only a Play, 2014RevivalCity, New York City]
-
A.
2022RevivalCity
Indicates a relationship where an entity is associated with a city that experienced a notable revival or renewal in the year 2022.
-
B.
2016RevivalCity
Indicates a relationship where an entity is associated with the 2016 revival of a city, such as being part of, contributing to, or resulting from that urban renewal event.
-
C.
revivalCity
chosen
Indicates the city where a revival, restoration, or renewed activity of something takes place.
-
D.
2014RevivalTheatre
Indicates a relationship where an entity is associated with a theatrical revival production that took place in 2014.
-
E.
revivalCenter
Indicates that an entity serves as a central place or hub where revival, restoration, or renewal activities for another entity occur.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.