Triple
T35180731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port |
E1015838
|
entity |
| Predicate | revivalProductionAt |
P182585
|
FINISHED |
| Object | National Theatre, London |
—
|
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: National Theatre, London | Statement: [Port, revivalProductionAt, National Theatre, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalProductionAt Context triple: [Port, revivalProductionAt, National Theatre, London]
-
A.
revivalVersionProducedFor
Indicates that a specific version of a revived work (such as a reboot, remake, or updated edition) was produced for a particular entity, context, or release.
-
B.
revivalAiredOnChannel
Indicates that a revival of a show or series was broadcast on a specific television channel.
-
C.
revivedBy
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
D.
revivalSpecialAired
Indicates that a special episode associated with a revival of a series or show has been broadcast.
-
E.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.