Triple
T15256082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campo de Hielo Sur |
E364649
|
entity |
| Predicate | borderDisputeTopic |
P105640
|
FINISHED |
| Object | demarcation of the international boundary |
—
|
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: demarcation of the international boundary | Statement: [Campo de Hielo Sur, borderDisputeTopic, demarcation of the international boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDisputeTopic Context triple: [Campo de Hielo Sur, borderDisputeTopic, demarcation of the international boundary]
-
A.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
borderIssue
chosen
Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
-
C.
borderConcern
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
-
D.
associatedTerritoryDispute
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
E.
frontierDispute
Indicates a conflict or disagreement between entities over the location, control, or status of a shared boundary or border.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084b97908190b3bf7ea7bd75bdc0 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.