Triple
T14880493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Raphia |
E349987
|
entity |
| Predicate | troopTypeUsed |
P6154
|
FINISHED |
| Object | phalanx infantry |
—
|
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: phalanx infantry | Statement: [Battle of Raphia, troopTypeUsed, phalanx infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: troopTypeUsed Context triple: [Battle of Raphia, troopTypeUsed, phalanx infantry]
-
A.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
B.
enemyForceType
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
C.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
D.
hasBattalionType
Indicates that an entity (such as a military unit) is associated with or classified by a specific type of battalion.
-
E.
typeOfUnitCommanded
Indicates the specific type or category of military or organizational unit that an entity is in command of.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e622388190b2bf91cd10b9821d |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.