Triple
T9963831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great North of Scotland Railway |
E195631
|
entity |
| Predicate | dateOfFirstSectionOpening |
P44081
|
FINISHED |
| Object | 1854 |
—
|
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: 1854 | Statement: [Great North of Scotland Railway, dateOfFirstSectionOpening, 1854]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstSectionOpening Context triple: [Great North of Scotland Railway, dateOfFirstSectionOpening, 1854]
-
A.
firstLineOpeningDate
chosen
Indicates the date on which the first line in a system, network, or service was officially opened or began operation.
-
B.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
C.
firstOpenedAt
Indicates the date and time at which something was initially opened for the first time.
-
D.
openingDateOfFirstSpan
Indicates the date on which the first span (e.g., of a structure or project) was initially opened or put into service.
-
E.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb71a33b48190a18c1a9023f249d2 |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.