Triple
T16222062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kut-al-Amara |
E393752
|
entity |
| Predicate | defendedByDuringWWI |
P43732
|
FINISHED |
| Object | British Indian Army garrison |
—
|
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: British Indian Army garrison | Statement: [Kut-al-Amara, defendedByDuringWWI, British Indian Army garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendedByDuringWWI Context triple: [Kut-al-Amara, defendedByDuringWWI, British Indian Army garrison]
-
A.
legalStatusDuringWWI
Indicates the legal condition or classification an entity held specifically during World War I (e.g., enemy alien, neutral, ally, civilian, combatant).
-
B.
roleInWorldWarI
chosen
Indicates the specific function, position, or involvement an entity had during World War I.
-
C.
controlledByDuringWWI
Indicates that one entity exercised political or military control over another entity specifically during the period of World War I.
-
D.
defensesDuringWorldWarII
Indicates that the subject engaged in or maintained defensive activities, measures, or structures during World War II.
-
E.
positionOnWorldWarI
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e227fcf058819099d5ff965cc2c267 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.