Triple
T17163902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivas Department |
E416554
|
entity |
| Predicate | borderTypeWithCostaRica |
P58557
|
FINISHED |
| Object | international land border |
—
|
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: international land border | Statement: [Rivas Department, borderTypeWithCostaRica, international land border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTypeWithCostaRica Context triple: [Rivas Department, borderTypeWithCostaRica, international land border]
-
A.
borderTypeWithVenezuela
Indicates the specific type or nature of the border that an entity shares with Venezuela.
-
B.
borderDirectionFromGuatemala
Indicates the cardinal or relative direction in which another country or region lies along Guatemala’s border.
-
C.
borderTownGuatemala
Indicates that a town is located on or near the national border of Guatemala, functioning as a border town relative to that country.
-
D.
borderTypeWithSpain
Indicates the type or nature of the border that an entity shares with Spain.
-
E.
countryBorderType
chosen
Indicates the type or nature of the border relationship that exists between two countries.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f913c84481908bb5da8bcc6a2e62 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.