Triple
T20258072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollandsche IJzeren Spoorweg-Maatschappij |
E498755
|
entity |
| Predicate | openingDateOfFirstLine |
P44081
|
FINISHED |
| Object | 1839 |
—
|
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: 1839 | Statement: [Hollandsche IJzeren Spoorweg-Maatschappij, openingDateOfFirstLine, 1839]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateOfFirstLine Context triple: [Hollandsche IJzeren Spoorweg-Maatschappij, openingDateOfFirstLine, 1839]
-
A.
openingDateToRapidTransit
Indicates the date on which a rapid transit service or connection was opened or became operational.
-
B.
firstSubwayOpeningDate
Indicates the calendar date on which a subway system or line first began operating.
-
C.
firstSubwayOpeningSegment
Indicates that the subject is the initial segment or section of a subway line that was opened first in its operation or construction sequence.
-
D.
firstLineOpeningDate
chosen
Indicates the date on which the first line in a system, network, or service was officially opened or began operation.
-
E.
openingDateToStreetcars
Indicates the date on which streetcar service began operating on or serving a particular location or route.
- F. None of above.
Provenance (3 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674c7296c819092860942de8f28d5 |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.