Triple
T2929086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highlands region |
E78915
|
entity |
| Predicate | transportChallenge |
P44003
|
FINISHED |
| Object | difficult road access |
—
|
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: difficult road access | Statement: [Highlands region, transportChallenge, difficult road access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportChallenge Context triple: [Highlands region, transportChallenge, difficult road access]
-
A.
transportAdvisory
Indicates that guidance, warnings, or recommendations are being issued regarding transportation conditions, operations, or usage.
-
B.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
C.
rides
Indicates that one entity travels on or is carried by another entity as a passenger or operator.
-
D.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
E.
transportIncludes
Indicates that a broader transport operation or service encompasses, contains, or makes use of a specific transport segment, mode, or component as part of its overall movement.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98002da4819098d6448eebcafad4 |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:55 p.m.