Triple
T35180734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port |
E1015838
|
entity |
| Predicate | revivalOpeningYear |
P91011
|
FINISHED |
| Object | 2013 |
—
|
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 | Statement: [Port, revivalOpeningYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalOpeningYear Context triple: [Port, revivalOpeningYear, 2013]
-
A.
revivalYear
chosen
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.
-
B.
revivalFirstAppearanceYear
Indicates the year in which a revival or renewed version of something first appeared or was introduced.
-
C.
revivalOriginalReleaseStart
Indicates the date or point in time when the original release associated with a later revival first began.
-
D.
2016RevivalOpeningYear
Indicates the calendar year in which a 2016 revival production was first opened or premiered.
-
E.
rediscoveryYear
Indicates the year in which something that was previously known but lost, forgotten, or overlooked was found or recognized again.
- 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_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.