Triple
T29128015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Paraitakene |
E738286
|
entity |
| Predicate | militaryFormationUsed |
P15598
|
FINISHED |
| Object | Macedonian phalanx |
—
|
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: Macedonian phalanx | Statement: [Battle of Paraitakene, militaryFormationUsed, Macedonian phalanx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryFormationUsed Context triple: [Battle of Paraitakene, militaryFormationUsed, Macedonian phalanx]
-
A.
militaryFormationOf
Indicates that one entity is a military unit or formation that is organizationally part of, or derived from, another entity.
-
B.
usedMilitaryFormation
chosen
Indicates that an entity employed a specific military formation or tactical arrangement of forces in a military context.
-
C.
militaryFormationNumber
Indicates the specific numerical designation assigned to a military formation within an armed force.
-
D.
tacticalFormation
Indicates a specific strategic arrangement or positioning of entities relative to one another to achieve a tactical objective.
-
E.
militaryFormationLevel
Indicates the hierarchical level or scale of a military formation within an armed forces organizational structure.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 11:29 a.m.