Triple
T500682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M74 motorway |
E10392
|
entity |
| Predicate | isKeyFreightRoute |
P14431
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [M74 motorway, isKeyFreightRoute, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyFreightRoute Context triple: [M74 motorway, isKeyFreightRoute, yes]
-
A.
containsShippingRoute
Indicates that one location or area includes within its boundaries a shipping route used for transporting goods or vessels.
-
B.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
C.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
D.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
E.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f13096248190a622a58dcf540b00 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebbd70481908b462296671de67b |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.