Triple
T5625652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Necho II |
E147709
|
entity |
| Predicate | outcomeOfBattle |
P19109
|
FINISHED |
| Object | defeated at the Battle of Carchemish (605 BCE) |
—
|
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: defeated at the Battle of Carchemish (605 BCE) | Statement: [Necho II, outcomeOfBattle, defeated at the Battle of Carchemish (605 BCE)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeOfBattle Context triple: [Necho II, outcomeOfBattle, defeated at the Battle of Carchemish (605 BCE)]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
battleOutcomeRole
Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
-
E.
tacticalOutcome
Indicates the specific result or consequence produced by a particular tactic or tactical action in a given 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02235b4e48190a529f70605bf47ca |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.