Triple
T28726182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentina and Bolivia |
E730228
|
entity |
| Predicate | borderPassesThrough |
P108342
|
FINISHED |
| Object | Salta Province (Argentina) |
—
|
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: Salta Province (Argentina) | Statement: [Argentina and Bolivia, borderPassesThrough, Salta Province (Argentina)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderPassesThrough Context triple: [Argentina and Bolivia, borderPassesThrough, Salta Province (Argentina)]
-
A.
borderPass
Indicates that one entity crosses or moves through the boundary separating two regions or jurisdictions.
-
B.
hasBorderThrough
chosen
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
C.
borderCrossingMode
Indicates the means or method by which a border is crossed between territories or jurisdictions.
-
D.
passesThroughArea
Indicates that an entity moves or extends through the spatial region defined by another entity or area.
-
E.
borderStraddling
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 28, 2026, 5:56 a.m.