Triple
T9088880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kadesh |
E217826
|
entity |
| Predicate | languageOfMainAccounts |
P60517
|
FINISHED |
| Object | Egyptian |
—
|
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: Egyptian | Statement: [Battle of Kadesh, languageOfMainAccounts, Egyptian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfMainAccounts Context triple: [Battle of Kadesh, languageOfMainAccounts, Egyptian]
-
A.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
B.
identityLanguage
Indicates that two language entities are identical or represent the same language.
-
C.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
D.
languageUsedAs
chosen
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
E.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
- 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.