Triple
T28058627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midland Railway network at Gloucester |
E709038
|
entity |
| Predicate | hadJunctionType |
P49487
|
FINISHED |
| Object | complex multi-route junction |
—
|
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: complex multi-route junction | Statement: [Midland Railway network at Gloucester, hadJunctionType, complex multi-route junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadJunctionType Context triple: [Midland Railway network at Gloucester, hadJunctionType, complex multi-route junction]
-
A.
hasJunctionType
chosen
Indicates the specific kind or classification of a junction associated with an entity.
-
B.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
C.
hasJunctionIn
Indicates that one entity contains or includes a junction located within the spatial or structural extent of another entity.
-
D.
isJunction
Indicates that an entity functions as a junction point where multiple paths, lines, or connections meet or intersect.
-
E.
hasJunctionName
Indicates that a junction (such as a road or rail intersection) is associated with a specific name.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fde4030819089d26a7e7c9d713e |
completed | May 2, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:38 p.m.