Triple
T21088483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John o' Groats |
E519566
|
entity |
| Predicate | routeEndpointOf |
P390
|
FINISHED |
| Object | Land's End to John o' Groats |
—
|
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: Land's End to John o' Groats | Statement: [John o' Groats, routeEndpointOf, Land's End to John o' Groats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeEndpointOf Context triple: [John o' Groats, routeEndpointOf, Land's End to John o' Groats]
-
A.
routeingPointFor
Indicates that one location or node serves as an intermediate routing point used to direct or forward traffic, goods, or information for another location or route.
-
B.
endPoint
chosen
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
C.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
D.
routeOperator
Indicates that an agent operates, manages, or is responsible for running a particular route or service path.
-
E.
routeUnder
Indicates that one route passes beneath another route or structure, typically at an underpass or similar crossing.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094cebe08190bb10f51a45c244ec |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.