Triple
T2917874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megiddo |
E78648
|
entity |
| Predicate | battleAssociation |
P23441
|
FINISHED |
| Object | Thutmose III’s victory over Canaanite coalition |
—
|
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: Thutmose III’s victory over Canaanite coalition | Statement: [Megiddo, battleAssociation, Thutmose III’s victory over Canaanite coalition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleAssociation Context triple: [Megiddo, battleAssociation, Thutmose III’s victory over Canaanite coalition]
-
A.
associatedWithBattle
chosen
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
-
B.
battleDateRelation
Indicates the temporal relationship specifying on which date a particular battle or combat event took place.
-
C.
associatedWithWar
Indicates a relationship where an entity is connected or related to war, such as by involvement, influence, cause, or context.
-
D.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
E.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:54 p.m.