Triple
T25451769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsal Head Viaduct |
E637799
|
entity |
| Predicate | transportModeCurrent |
P86086
|
FINISHED |
| Object | non-motorised trail |
—
|
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: non-motorised trail | Statement: [Monsal Head Viaduct, transportModeCurrent, non-motorised trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeCurrent Context triple: [Monsal Head Viaduct, transportModeCurrent, non-motorised trail]
-
A.
transportModePresent
chosen
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
B.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
C.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
-
D.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
E.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 2:03 p.m.