Triple
T28279207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stourbridge Junction |
E713092
|
entity |
| Predicate | branchLineLength |
P39661
|
FINISHED |
| Object | approximately 0.8 miles |
—
|
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: approximately 0.8 miles | Statement: [Stourbridge Junction, branchLineLength, approximately 0.8 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchLineLength Context triple: [Stourbridge Junction, branchLineLength, approximately 0.8 miles]
-
A.
branchLine
Indicates a relationship where one line, route, or path diverges from and is subordinate to a main or primary line.
-
B.
branchLineDirection
Indicates the directional orientation or flow of a branch line relative to a main line or reference point.
-
C.
lineLengthType
Indicates the type or category used to characterize the length of a line.
-
D.
hasBranchLinePurpose
Indicates that a branch line is associated with a specific intended function or purpose within a larger network or system.
-
E.
hasLineLength
chosen
Indicates that one entity has, is characterized by, or is associated with a specific line length value.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6444debc88190a2799fedc421013a |
completed | May 2, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:21 p.m.