Triple
T3050968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broomloan Depot |
E83569
|
entity |
| Predicate | railGaugeServed |
P5070
|
FINISHED |
| Object | standard gauge test track |
—
|
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: standard gauge test track | Statement: [Broomloan Depot, railGaugeServed, standard gauge test track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railGaugeServed Context triple: [Broomloan Depot, railGaugeServed, standard gauge test track]
-
A.
usesRailGauge
chosen
Indicates that one entity (typically a railway system or line) operates using the specified rail gauge measurement of the other entity.
-
B.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
C.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
-
D.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
E.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bb1a46081908547a2f27cbf3446 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.