Triple
T1145589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Pyramids |
E23556
|
entity |
| Predicate | usedFormation |
P15598
|
FINISHED |
| Object | divisional square formation |
—
|
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: divisional square formation | Statement: [Battle of the Pyramids, usedFormation, divisional square formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFormation Context triple: [Battle of the Pyramids, usedFormation, divisional square formation]
-
A.
usedMilitaryFormation
chosen
Indicates that an entity employed a specific military formation or tactical arrangement of forces in a military context.
-
B.
typicalFormation
Indicates the usual or characteristic way in which something is formed, structured, or comes into existence.
-
C.
formsSwarms
Indicates that multiple entities come together to create or participate in a coordinated swarm.
-
D.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
E.
isMajorFormation
Indicates that something constitutes a primary or principal structural unit or phase within a larger system, sequence, or process.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc51244c8190bcd533f3e80c8f17 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.