Triple
T37387387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Salvador–Honduras border |
E928605
|
entity |
| Predicate | demarcationCompletedYear |
P121045
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [El Salvador–Honduras border, demarcationCompletedYear, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demarcationCompletedYear Context triple: [El Salvador–Honduras border, demarcationCompletedYear, 2006]
-
A.
lastDelimitationYear
Indicates the year in which the most recent boundary or delimitation of the entity was officially established or updated.
-
B.
yearOfFinalDemarcation
chosen
Indicates the specific year in which a boundary, limit, or division was formally and definitively established.
-
C.
demarcationStatus
Indicates the current state or condition of how clearly and officially a boundary or division between entities is defined or marked.
-
D.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
E.
yearOfStandardization
Indicates the specific year in which something was formally standardized or officially adopted as a standard.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.