Triple
T16208007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Circle (Glasgow Subway) |
E393377
|
entity |
| Predicate | hasLoopConfiguration |
P122164
|
FINISHED |
| Object | double-track loop |
—
|
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: double-track loop | Statement: [Inner Circle (Glasgow Subway), hasLoopConfiguration, double-track loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoopConfiguration Context triple: [Inner Circle (Glasgow Subway), hasLoopConfiguration, double-track loop]
-
A.
hasLoopMode
Indicates that an entity operates or is configured in a mode where its behavior or process repeats in a loop.
-
B.
hasLoopRole
Indicates that an entity participates in a loop structure with a specific functional role within that loop.
-
C.
hasLoopDirectionOptions
Indicates that an entity provides or supports multiple possible directions in which a loop can operate or be executed.
-
D.
hasPassingLoopAt
Indicates that a railway line or track segment includes a passing loop located at a specified place or point.
-
E.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
- F. None of above. chosen
Provenance (4 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22710ef2c8190a8d7b9fb1666816c |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.