Triple
T24449155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewis Pass |
E616482
|
entity |
| Predicate | regionBoundary |
P10768
|
FINISHED |
| Object | Canterbury–West Coast boundary nearby |
—
|
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: Canterbury–West Coast boundary nearby | Statement: [Lewis Pass, regionBoundary, Canterbury–West Coast boundary nearby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionBoundary Context triple: [Lewis Pass, regionBoundary, Canterbury–West Coast boundary nearby]
-
A.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
B.
borderRegionOf
chosen
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
C.
boundaryUnit
Indicates that one entity serves as a boundary-defining unit or segment that delimits the extent or limits of another entity.
-
D.
boundaryName
Indicates the designated name or label assigned to a specific boundary or border between entities.
-
E.
geographicBoundary
Indicates that one entity serves as a limiting border or edge that defines the geographic extent or separation of another entity.
- 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298562c6c8190a7374508f7237be2 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.