Triple
T36240131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namibia–Angola border |
E891495
|
entity |
| Predicate | demarcationInfluencedBy |
P160803
|
FINISHED |
| Object | river courses |
—
|
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: river courses | Statement: [Namibia–Angola border, demarcationInfluencedBy, river courses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demarcationInfluencedBy Context triple: [Namibia–Angola border, demarcationInfluencedBy, river courses]
-
A.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
B.
demarcationStatus
Indicates the current state or condition of how clearly and officially a boundary or division between entities is defined or marked.
-
C.
hasDemarcationAuthority
Indicates that an entity possesses the formal power or right to define, set, or modify boundaries or divisions between areas, responsibilities, or categories.
-
D.
delimitationAffectedIn
chosen
Indicates that one entity’s delimitation or boundary definition is influenced, altered, or impacted by another entity.
-
E.
wasDemarcatedBetween
Indicates that a boundary or dividing line was formally established separating one entity from another.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5ceb6a081909c40f5f3fff9bcbd |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.