Triple
T28988559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minqar Qaim |
E734758
|
entity |
| Predicate | belligerentInArea |
P10155
|
FINISHED |
| Object | British Eighth Army |
—
|
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: British Eighth Army | Statement: [Minqar Qaim, belligerentInArea, British Eighth Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belligerentInArea Context triple: [Minqar Qaim, belligerentInArea, British Eighth Army]
-
A.
belligerentControl
Indicates that one party exercises control, authority, or coercive influence over another in a hostile or conflict-oriented context.
-
B.
belligerentFor
Indicates a relationship in which one entity is engaged in hostile or aggressive behavior toward, or in conflict with, another entity.
-
C.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
-
D.
conflictBelligerent
chosen
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
-
E.
allegedBelligerent
Indicates that one entity is claimed or accused of being a hostile or warring party in relation to another entity or conflict.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65f7bc2748190bced1b468962b99d |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:15 a.m.