Triple
T11067454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramides |
E261661
|
entity |
| Predicate | line14OpeningDate |
P97617
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Pyramides, line14OpeningDate, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: line14OpeningDate Context triple: [Pyramides, line14OpeningDate, 1998]
-
A.
line4OpeningDate
Indicates the date on which the fourth line (e.g., of a transit system or network) was officially opened or began operation.
-
B.
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.
-
C.
line13OpeningDate
Indicates the date on which line 13 was officially opened or began operation.
-
D.
line12OpeningDate
Indicates the date on which line 12 was opened or began operation.
-
E.
line2OpeningDate
Indicates the date on which the second line (e.g., a route, service, or facility line) was officially 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79920428c81908db824ab54e08e8d |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.