Triple
T12734447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McDermitt |
E304325
|
entity |
| Predicate | borderCommunity |
P55550
|
FINISHED |
| Object | Nevada–Oregon border town |
—
|
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: Nevada–Oregon border town | Statement: [McDermitt, borderCommunity, Nevada–Oregon border town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCommunity Context triple: [McDermitt, borderCommunity, Nevada–Oregon border town]
-
A.
crossBorderCommunity
chosen
Indicates a relationship where a community spans or connects populations across one or more political or geographic borders.
-
B.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
C.
borderStreet
Indicates that a street forms or lies along the boundary between two geographic areas or properties.
-
D.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
E.
borderedBy
Indicates that one entity shares a common boundary or edge with 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.