Triple
T9088873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kadesh |
E217826
|
entity |
| Predicate | HittiteAllies |
P16682
|
FINISHED |
| Object | Syrian vassal states |
—
|
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: Syrian vassal states | Statement: [Battle of Kadesh, HittiteAllies, Syrian vassal states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HittiteAllies Context triple: [Battle of Kadesh, HittiteAllies, Syrian vassal states]
-
A.
alliesInWar
chosen
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
B.
laterAlliesWith
Indicates that two entities become allies at a later time, after not being allied initially.
-
C.
historicallyAlliedWith
Indicates that two entities have been political, military, or strategic allies during some period in the past.
-
D.
soughtAllianceWith
Indicates that one entity actively attempted to form an alliance or cooperative partnership with another entity.
-
E.
majorAllies
Indicates that the entities are principal or primary allies, signifying a strong, significant, and mutually supportive alliance between them.
- 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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9657d48081909e0ae0f1fa8ff599 |
completed | April 1, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:14 p.m.