Triple
T31346361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amhara regional forces |
E799456
|
entity |
| Predicate | allegationStatus |
P84014
|
FINISHED |
| Object | contested |
—
|
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: contested | Statement: [Amhara regional forces, allegationStatus, contested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegationStatus Context triple: [Amhara regional forces, allegationStatus, contested]
-
A.
allegedStatus
Indicates that a particular status or condition is claimed or asserted about an entity, but has not been confirmed as true.
-
B.
hasAllegationsOf
Indicates that one entity is accused or suspected of engaging in certain actions, behaviors, or misconduct, but without implying that these accusations are proven.
-
C.
deniedAllegations
Indicates that one party has rejected or refuted specific accusations made against them.
-
D.
statusOfClaim
chosen
Indicates the current state or condition of a specific claim within a process or system.
-
E.
allegationByComplainant
Indicates that a specific allegation is made or asserted by the complainant against another party or situation.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 29, 2026, 9:17 p.m.