Triple
T34497176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strensall railway station |
E885636
|
entity |
| Predicate | lineStillOpen |
P74694
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Strensall railway station, lineStillOpen, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineStillOpen Context triple: [Strensall railway station, lineStillOpen, yes]
-
A.
openingLineStatus
Indicates the status or condition of an entity’s opening line, such as whether it exists, is valid, or meets a specified criterion.
-
B.
lineBOpened
Indicates that a specific line B has been opened or activated, transitioning from a closed or inactive state.
-
C.
lineStatus
chosen
Indicates the current operational or functional state of a line or connection within a system.
-
D.
lineMaintained
Indicates that a particular line (such as a route, connection, or service) is kept in proper working condition through ongoing maintenance activities.
-
E.
line8Status
Indicates the status or condition associated with the eighth line in a sequence, record, or structured data set.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.