Triple
T37297905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pigalle metro station |
E925853
|
entity |
| Predicate | openingDateOnLine12 |
P193976
|
FINISHED |
| Object | 1911-04-08 |
—
|
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: 1911-04-08 | Statement: [Pigalle metro station, openingDateOnLine12, 1911-04-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateOnLine12 Context triple: [Pigalle metro station, openingDateOnLine12, 1911-04-08]
-
A.
openingDateOnLine
Indicates the date on which a particular service, facility, or segment first began operating on a specified line.
-
B.
openingDateLineA
Indicates the date on which Line A officially began operating or was opened.
-
C.
openingDateLine15
Indicates the date on which line 15 (e.g., a specific route, service, or infrastructure segment) was officially opened or began operation.
-
D.
openingDateLine10
Indicates the date on which line 10 (e.g., a specific route, service, or infrastructure line) was officially opened or began operation.
-
E.
openingDateLine14
Indicates the date on which something (such as a service, facility, or record) is opened or begins operation, as specified in line 14 of a form or document.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: May 3, 2026, 4:16 p.m.