Triple
T2940126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IND |
E79364
|
entity |
| Predicate | firstLineOpeningDate |
P44081
|
FINISHED |
| Object | September 10, 1932 |
—
|
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: September 10, 1932 | Statement: [IND, firstLineOpeningDate, September 10, 1932]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLineOpeningDate Context triple: [IND, firstLineOpeningDate, September 10, 1932]
-
A.
firstOpenedAt
Indicates the date and time at which something was initially opened for the first time.
-
B.
firstLineOpened
Indicates that the first line of something (e.g., a document, file, or text block) has been opened or accessed.
-
C.
line4OpeningDate
Indicates the date on which the fourth line (e.g., of a transit system or network) was officially opened or began operation.
-
D.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
E.
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.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad986f38948190a636a826693a9d4f |
completed | March 8, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:56 p.m.