Triple
T25451733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsal Head Viaduct |
E637799
|
entity |
| Predicate | builtForLine |
P8196
|
FINISHED |
| Object | Midland Railway |
—
|
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: Midland Railway | Statement: [Monsal Head Viaduct, builtForLine, Midland Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtForLine Context triple: [Monsal Head Viaduct, builtForLine, Midland Railway]
-
A.
builtLine
Indicates that an entity constructed or established a particular line, such as a route, boundary, or infrastructure segment.
-
B.
isBuiltFor
chosen
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
C.
carriedByLine
Indicates that something (such as a service, signal, or connection) is transported or conveyed via a particular line or conduit.
-
D.
builtToMark
Indicates that something was constructed for the purpose of commemorating, signaling, or designating a particular event, place, boundary, or significance.
-
E.
engineeredForLabel
Indicates that something has been specifically designed, adapted, or optimized to serve, support, or be used for the referenced label or purpose.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f707c8408190b0405250a2c02a03 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:03 p.m.