Triple
T36402171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon boundary dispute |
E896659
|
entity |
| Predicate | U.S.ClaimedBoundary |
P185439
|
FINISHED |
| Object | north to latitude 54°40′ N |
—
|
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: north to latitude 54°40′ N | Statement: [Oregon boundary dispute, U.S.ClaimedBoundary, north to latitude 54°40′ N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: U.S.ClaimedBoundary Context triple: [Oregon boundary dispute, U.S.ClaimedBoundary, north to latitude 54°40′ N]
-
A.
USStateBorderFor
Indicates that a U.S. state serves as a bordering state for the specified geographic or political entity.
-
B.
westernBoundaryReference
Indicates the reference feature or limit that defines the western boundary of an entity or area.
-
C.
legalStatusOfBorders
Indicates the legal status or recognition of a defined border between territories or jurisdictions.
-
D.
borderingPoliticalEntityNorth
Indicates that one political entity lies directly to the north of, and shares a border with, another political entity.
-
E.
isPoliticalBoundary
Indicates that one entity serves as a dividing line or border that separates distinct political or administrative jurisdictions.
- F. None of above. chosen
Provenance (4 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.