Triple
T31979666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Army |
E816541
|
entity |
| Predicate | sentExpeditionaryForce |
P17798
|
FINISHED |
| Object | Kagnew Battalion |
—
|
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: Kagnew Battalion | Statement: [Imperial Army, sentExpeditionaryForce, Kagnew Battalion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentExpeditionaryForce Context triple: [Imperial Army, sentExpeditionaryForce, Kagnew Battalion]
-
A.
sentEmbassyTo
Indicates that one entity dispatched an official diplomatic mission or embassy to another entity.
-
B.
sentMissionTo
chosen
Indicates that one entity dispatched or assigned another entity to carry out a specific mission at a particular destination or context.
-
C.
sentOnMissionWith
Indicates that one entity was assigned or dispatched to a mission together with another entity as companions or teammates.
-
D.
commandedForcesAgainst
Indicates that one entity held command authority over military or armed forces engaged in opposition to another entity.
-
E.
sentOnMissionBy
Indicates that one entity was assigned or dispatched on a mission by another entity.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b348d01c8190afa1fe9ece4de11a |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:11 a.m.