Triple
T15779267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyon Metro line D |
E382568
|
entity |
| Predicate | hasExtensionOpeningDate |
P119981
|
FINISHED |
| Object | 1992-12-11 |
—
|
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: 1992-12-11 | Statement: [Lyon Metro line D, hasExtensionOpeningDate, 1992-12-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExtensionOpeningDate Context triple: [Lyon Metro line D, hasExtensionOpeningDate, 1992-12-11]
-
A.
extensionOpeningPeriod
Indicates the time span during which an extension (such as a facility, service, or feature) is open or available for use.
-
B.
northLineExtensionOpeningDate
Indicates the date on which the extension of the North Line officially opened for service.
-
C.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
D.
hasOpenedFor
Indicates that one entity has performed or appeared as the opening act or preliminary participant for another entity, typically in an event or performance context.
-
E.
softOpeningDate
Indicates the date on which a business, venue, or service begins limited or trial operations before its official grand opening.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e053fea90081908e3fe4f91475bead |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e006b17f7881908b8c7a37f0af4581 |
completed | April 15, 2026, 9:44 p.m. |
Created at: April 10, 2026, 4:48 a.m.