Triple
T29538966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Delta |
E749434
|
entity |
| Predicate | strategicObjectiveOfSeaPeoples |
P129227
|
FINISHED |
| Object | invasion of Egypt |
—
|
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: invasion of Egypt | Statement: [Battle of the Delta, strategicObjectiveOfSeaPeoples, invasion of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicObjectiveOfSeaPeoples Context triple: [Battle of the Delta, strategicObjectiveOfSeaPeoples, invasion of Egypt]
-
A.
strategicObjectiveOttoman
Indicates that one entity serves as or relates to a strategic objective or goal specifically concerning the Ottoman Empire.
-
B.
militaryObjectiveOf
chosen
Indicates that something serves as a military target, goal, or purpose specifically associated with a given actor or force.
-
C.
goalOfCarthaginians
Indicates that the specified objective or aim is held or pursued by the Carthaginians.
-
D.
primaryObjectiveOfEmpire
Indicates the main strategic goal or overarching purpose that an empire seeks to achieve or maintain.
-
E.
objectiveOfEgypt
Indicates that something is the goal, aim, or intended outcome pursued by Egypt.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 5 p.m.