Triple
T15060859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Megiddo |
E379620
|
entity |
| Predicate | tacticUsedByEgypt |
P100860
|
FINISHED |
| Object | surprise march through the Aruna pass |
—
|
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: surprise march through the Aruna pass | Statement: [Battle of Megiddo, tacticUsedByEgypt, surprise march through the Aruna pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticUsedByEgypt Context triple: [Battle of Megiddo, tacticUsedByEgypt, surprise march through the Aruna pass]
-
A.
combatantStrengthEgyptian
Indicates that the entity has combatant strength or military capability associated with Egyptian forces or context.
-
B.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
C.
strategicRationaleForEgypt
Indicates that something serves as a strategic justification, motive, or reasoning specifically related to actions, policies, or decisions involving Egypt.
-
D.
opponentAtBattleOfTheNile
Indicates that one entity was an opposing combatant of the other in the Battle of the Nile.
-
E.
tacticalFeatureUsed
chosen
Indicates that a specific tactical feature, maneuver, or capability is employed or brought into play within a tactical situation or operation.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedee6a55c8190b40c4672fb46b79b |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:01 a.m.