Triple
T9088881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kadesh |
E217826
|
entity |
| Predicate | languageOfTreatyAftermath |
P87118
|
FINISHED |
| Object | Akkadian |
—
|
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: Akkadian | Statement: [Battle of Kadesh, languageOfTreatyAftermath, Akkadian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfTreatyAftermath Context triple: [Battle of Kadesh, languageOfTreatyAftermath, Akkadian]
-
A.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
B.
historicalTreaty
Indicates that a formal agreement or pact was established between entities at some point in the past.
-
C.
treatyAlsoKnownAs
Indicates that a treaty is referred to by an alternative name or alias.
-
D.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
-
E.
wasDividedByTreaty
Indicates that an entity (such as a territory or region) was partitioned or separated as the result of a formal treaty or agreement.
- 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_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. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:14 p.m.