Triple
T32590174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horseshoe Bay–Langdale ferry route |
E833040
|
entity |
| Predicate | nearbyCommunityToLangdale |
P4647
|
FINISHED |
| Object | Gibsons |
—
|
NE NERFINISHED |
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: Gibsons | Statement: [Horseshoe Bay–Langdale ferry route, nearbyCommunityToLangdale, Gibsons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCommunityToLangdale Context triple: [Horseshoe Bay–Langdale ferry route, nearbyCommunityToLangdale, Gibsons]
-
A.
nearbyFell
Indicates that one entity fell or collapsed in close physical proximity to another entity or reference point.
-
B.
nearParish
Indicates that one entity is geographically close to or in the vicinity of a specified parish.
-
C.
hasNearbyCommunity
chosen
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
D.
nearbyCanyon
Indicates that one entity is located close to a canyon in spatial proximity.
-
E.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 1, 2026, 1:05 a.m.