Triple
T37966332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mughar Ridge |
E947152
|
entity |
| Predicate | notableUnitAction |
—
|
GENERATED |
| Object | mounted charge by Yeomanry Mounted Division |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUnitAction Context triple: [Battle of Mughar Ridge, notableUnitAction, mounted charge by Yeomanry Mounted Division]
-
A.
notableActionAt
Indicates that an entity performed or was involved in a significant action or event at a specific location or point in time.
-
B.
notableCommanderAtAction
Indicates that a particular commander is notably associated with leading or playing a significant command role in a specific action or event.
-
C.
notableUnitHistory
Indicates that there is a historically significant event, role, or period associated with the unit.
-
D.
notableDeed
chosen
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
E.
notableAirOperation
Indicates that there is a significant or historically important air operation associated with the subject.
- F. None of above.
Provenance (1 batch)
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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.