Triple
T28726171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentina and Bolivia |
E730228
|
entity |
| Predicate | borderUsedFor |
P193934
|
FINISHED |
| Object | regional trade |
—
|
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: regional trade | Statement: [Argentina and Bolivia, borderUsedFor, regional trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderUsedFor Context triple: [Argentina and Bolivia, borderUsedFor, regional trade]
-
A.
borderConceptUsedBy
Indicates that a conceptual boundary or limit is employed or referenced by another entity in its definition, use, or interpretation.
-
B.
usedAsBorder
Indicates that one entity functions as a boundary or dividing line for another entity.
-
C.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
D.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
E.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 28, 2026, 5:56 a.m.