Triple
T12251098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orléans tramway |
E291971
|
entity |
| Predicate | lineBOpened |
P103728
|
FINISHED |
| Object | 29 June 2012 |
—
|
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: 29 June 2012 | Statement: [Orléans tramway, lineBOpened, 29 June 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineBOpened Context triple: [Orléans tramway, lineBOpened, 29 June 2012]
-
A.
originalLineOpened
Indicates that a transportation or service line began its initial operation or was first opened for use.
-
B.
lineOpeningContext
Indicates the contextual situation or circumstances present at the moment a line (e.g., of dialogue, text, or code) begins.
-
C.
lineOpeningPhase
Indicates the phase or stage during which a line (such as a service, process, or system) is initially opened or brought into operation.
-
D.
line3OpeningSegment
Indicates that something is the initial or opening segment of a third line in a sequence or structure.
-
E.
openingLineStatus
Indicates the status or condition of an entity’s opening line, such as whether it exists, is valid, or meets a specified criterion.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d91d3654208190a2e0487dfa1d54da |
completed | April 10, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:52 p.m.