Triple
T34236373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowdham railway station |
E878344
|
entity |
| Predicate | serviceOperatorHistory |
P28596
|
FINISHED |
| Object | British Rail (historical) |
—
|
NE NERFINISHED |
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: British Rail (historical) | Statement: [Lowdham railway station, serviceOperatorHistory, British Rail (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceOperatorHistory Context triple: [Lowdham railway station, serviceOperatorHistory, British Rail (historical)]
-
A.
operationalHistory
Indicates the record of how something has been used, functioned, or operated over time, including its past activities and events.
-
B.
operatorHistory
chosen
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
C.
serviceHistory
Indicates the record of past services, maintenance, or support actions that have been performed over time.
-
D.
platformHistory
Indicates a relationship where one entity records or represents the historical states, changes, or evolution of a platform over time.
-
E.
equipmentHistory
Indicates that there exists a historical record linking an entity to equipment it has used, owned, or been associated with over time.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 1, 2026, 1:56 a.m.