Triple
T8107266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opéra-Comique |
E189257
|
entity |
| Predicate | predecessorBuildingCompletedIn |
P59253
|
FINISHED |
| Object | 1840 |
—
|
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: 1840 | Statement: [Opéra-Comique, predecessorBuildingCompletedIn, 1840]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorBuildingCompletedIn Context triple: [Opéra-Comique, predecessorBuildingCompletedIn, 1840]
-
A.
predecessorBuildingDate
chosen
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
B.
towerCompletedBefore
Indicates that the construction or completion of one tower occurred earlier in time than the construction or completion of another tower.
-
C.
successorBuildingOnSite
Indicates that one building directly replaces another on the same physical site or location.
-
D.
predecessorProject
Indicates that one project temporally or logically comes before and leads into another project in a sequence or dependency chain.
-
E.
laterBuiltOverBy
Indicates that a structure or feature was constructed at a later time on top of, or replacing, an earlier one.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42f89dd481908f1a25e4b16a8fc8 |
completed | March 31, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69cb04a2ed1c8190b73562321ad688bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:32 p.m.