Triple
T25377584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multinational Force of Central Africa |
E633094
|
entity |
| Predicate | drawsTroopsFrom |
P15397
|
FINISHED |
| Object | Central African states |
—
|
NE NERFINISHED |
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: Central African states | Statement: [Multinational Force of Central Africa, drawsTroopsFrom, Central African states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drawsTroopsFrom Context triple: [Multinational Force of Central Africa, drawsTroopsFrom, Central African states]
-
A.
suppliedTroopsTo
chosen
Indicates that one entity provided military personnel or forces to another entity.
-
B.
commandedTroopsAt
Indicates that a person held command authority over military forces at a specific location or during a particular operation.
-
C.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
D.
peakTroopDeployment
Indicates the maximum number of troops that were deployed at any single point during a specified conflict or operation.
-
E.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 1:38 p.m.