Triple
T25822683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States borders |
E650442
|
entity |
| Predicate | includesBorderRegion |
P57389
|
FINISHED |
| Object | United States–Canada border |
—
|
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: United States–Canada border | Statement: [United States borders, includesBorderRegion, United States–Canada border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBorderRegion Context triple: [United States borders, includesBorderRegion, United States–Canada border]
-
A.
borderRegionsInclude
chosen
Indicates that the specified border area encompasses or contains the referenced regions within its boundaries.
-
B.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
E.
borderIncludesEnclaveRegion
Indicates that a border surrounds or contains an enclave region within its boundaries.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 22, 2026, 7:30 a.m.