Triple
T8720388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concorde (Paris Métro) |
E206994
|
entity |
| Predicate | line12OpeningDate |
P84261
|
FINISHED |
| Object | 1910-11-05 |
—
|
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: 1910-11-05 | Statement: [Concorde (Paris Métro), line12OpeningDate, 1910-11-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: line12OpeningDate Context triple: [Concorde (Paris Métro), line12OpeningDate, 1910-11-05]
-
A.
line2OpeningDate
Indicates the date on which the second line (e.g., a route, service, or facility line) was officially opened or began operation.
-
B.
line13OpeningDate
Indicates the date on which line 13 was officially opened or began operation.
-
C.
openingDate_Line2
Indicates the secondary or alternative date on which something (such as a facility, service, or event) is opened or becomes operational.
-
D.
line3OpeningDate
Indicates the calendar date on which the third line (e.g., a route, service line, or similar system component) was officially opened or began operation.
-
E.
line10OpeningDate
Indicates the date on which line 10 was first opened or began operation.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d02a52c81909f93622ae6920b80 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:36 p.m.