Triple
T31670049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pasayten Wilderness |
E808246
|
entity |
| Predicate | easternExtentOf |
P4240
|
FINISHED |
| Object | North Cascades |
—
|
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: North Cascades | Statement: [Pasayten Wilderness, easternExtentOf, North Cascades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternExtentOf Context triple: [Pasayten Wilderness, easternExtentOf, North Cascades]
-
A.
easternmostPartOf
Indicates that one entity is the geographically furthest-east portion or segment of another entity.
-
B.
easternTerminusAtBorderWith
Indicates that something’s eastern endpoint or final location lies at, or directly on, a border shared with another entity.
-
C.
easternBoundaryFormedBy
Indicates that the eastern boundary of an area, region, or object is defined or formed by a specified feature or entity.
-
D.
easternTerminusRegion
Indicates the region in which something (such as a route, line, or path) has its eastern endpoint or terminus.
-
E.
locatedEastOf
chosen
Indicates that one entity is positioned geographically to the east 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:01 p.m.