Triple
T29620195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malawi–Tanzania border |
E754972
|
entity |
| Predicate | disputeFocus |
P107087
|
FINISHED |
| Object | territorial claims in Lake Malawi |
—
|
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: territorial claims in Lake Malawi | Statement: [Malawi–Tanzania border, disputeFocus, territorial claims in Lake Malawi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeFocus Context triple: [Malawi–Tanzania border, disputeFocus, territorial claims in Lake Malawi]
-
A.
focusIssue
Indicates that an issue, topic, or problem is the primary subject of attention or concern in a given context.
-
B.
argumentFocus
Indicates that a particular argument within a relation or event is being highlighted as the primary focus or point of emphasis.
-
C.
disputeIssue
chosen
Indicates that there is a disagreement or conflict specifically concerning a particular issue or point of contention.
-
D.
importFocus
Indicates that attention, priority, or emphasis is being brought into or concentrated on a particular entity or aspect.
-
E.
focusShift
Indicates a change in attention or emphasis from one entity or topic to 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:34 p.m.