Triple
T7135762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnstaple railway station |
E166301
|
entity |
| Predicate | hasMapContext |
P18937
|
FINISHED |
| Object | United Kingdom Barnstaple |
—
|
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: United Kingdom Barnstaple | Statement: [Barnstaple railway station, hasMapContext, United Kingdom Barnstaple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapContext Context triple: [Barnstaple railway station, hasMapContext, United Kingdom Barnstaple]
-
A.
hasMapReference
chosen
Indicates that an entity is associated with a specific map or map location reference.
-
B.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
-
C.
hasCanonicalContext
Indicates that something is associated with its primary, standard, or officially recognized contextual setting or framework.
-
D.
hasTransportContext
Indicates that there exists a transportation-related situation, setting, or conditions under which the associated entities or actions take place.
-
E.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e690f954819084b81a555f4cdb5e |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.