Triple
T29538965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Delta |
E749434
|
entity |
| Predicate | opposingForceDescription |
P180717
|
FINISHED |
| Object | coalition of Sea Peoples |
—
|
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: coalition of Sea Peoples | Statement: [Battle of the Delta, opposingForceDescription, coalition of Sea Peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingForceDescription Context triple: [Battle of the Delta, opposingForceDescription, coalition of Sea Peoples]
-
A.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
B.
opposingForcesStatus
Indicates the current state or condition of two or more forces that are in conflict or opposition to each other.
-
C.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
D.
opposedWarfareType
Indicates that one entity is in opposition to, or acts against, the type or form of warfare represented by the other entity.
-
E.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
- F. None of above. chosen
Provenance (4 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_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 28, 2026, 5 p.m.