Triple
T3713397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Potidaea |
E81467
|
entity |
| Predicate | hasMilitaryAction |
P35485
|
FINISHED |
| Object | land battle |
—
|
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: land battle | Statement: [Battle of Potidaea, hasMilitaryAction, land battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryAction Context triple: [Battle of Potidaea, hasMilitaryAction, land battle]
-
A.
wasMilitarized
Indicates that an entity underwent a process of being organized, equipped, or adapted for military use or purposes.
-
B.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
C.
militaryActivity
chosen
Indicates that an entity is engaged in, associated with, or affected by actions, operations, or preparations conducted by armed forces.
-
D.
hasNotableWar
Indicates that an entity is associated with a significant or historically important war.
-
E.
militaryForceUsed
Indicates that one entity employs or applies military power or armed force against, within, or in relation to another entity or situation.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc9ccfad081908730ed15c6f87ce2 |
completed | March 8, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.