Triple
T3438300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caledonian MacBrayne |
E72507
|
entity |
| Predicate | routeNetworkSize |
P29564
|
FINISHED |
| Object | over 20 routes |
—
|
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: over 20 routes | Statement: [Caledonian MacBrayne, routeNetworkSize, over 20 routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeNetworkSize Context triple: [Caledonian MacBrayne, routeNetworkSize, over 20 routes]
-
A.
networkLength
Indicates the total measured extent or distance covered by a network (e.g., of connections, links, or paths).
-
B.
numberOfRoutes
chosen
Indicates the total count of distinct routes or paths associated with a given entity or between specified entities.
-
C.
routeNetworkCharacteristic
Indicates a relationship where a specific characteristic or property is attributed to a route within a network.
-
D.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
-
E.
roadSystemLength
Indicates the total length or extent of a road network associated with an entity.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f575cc8190866929b1e8930143 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.