Triple
T13913457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Megiddo (609 BCE) |
E334555
|
entity |
| Predicate | hasResultingEvent |
P33358
|
FINISHED |
| Object | Necho II’s continued march toward Carchemish |
—
|
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: Necho II’s continued march toward Carchemish | Statement: [Battle of Megiddo (609 BCE), hasResultingEvent, Necho II’s continued march toward Carchemish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResultingEvent Context triple: [Battle of Megiddo (609 BCE), hasResultingEvent, Necho II’s continued march toward Carchemish]
-
A.
hasEventOutcome
chosen
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
B.
hasDeterminingEvent
Indicates that one event or occurrence serves as the decisive cause, condition, or basis that determines another situation, outcome, or state.
-
C.
hasSideEvent
Indicates that an event is associated with an additional, related side event occurring alongside it.
-
D.
hasResultingChange
Indicates that one entity causes or leads to a specific change or transformation in another entity or state.
-
E.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential order.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27245c648190b2946845ce0fdbf8 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.