Triple
T15831414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opéra National de Lyon |
E383879
|
entity |
| Predicate | originalBuildingCompletionDate |
P23965
|
FINISHED |
| Object | 1831 |
—
|
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: 1831 | Statement: [Opéra National de Lyon, originalBuildingCompletionDate, 1831]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBuildingCompletionDate Context triple: [Opéra National de Lyon, originalBuildingCompletionDate, 1831]
-
A.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
B.
constructionDate
chosen
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
-
C.
predecessorBuildingDate
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
D.
claimedConstructionDate
Indicates the date on which an entity is asserted or reported to have been constructed, according to some claim or source.
-
E.
originalBuildingConstructed
Indicates that a particular building was initially constructed in its original form or configuration.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e6433ac8190a3d3e0d573673ea3 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.