Triple
T30551255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amun division |
E777564
|
entity |
| Predicate | roleInBattleOfKadesh |
P28183
|
FINISHED |
| Object | principal Egyptian field division |
—
|
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: principal Egyptian field division | Statement: [Amun division, roleInBattleOfKadesh, principal Egyptian field division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfKadesh Context triple: [Amun division, roleInBattleOfKadesh, principal Egyptian field division]
-
A.
roleInBattleOfMuʾtah
Indicates the specific role or involvement an entity had in the Battle of Muʾtah.
-
B.
sideInBattleOfYarmouk
Indicates that an entity participated as a side (belligerent) in the Battle of Yarmouk.
-
C.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
D.
roleInPunicWars
Indicates the specific involvement, function, or position an entity had in the events or campaigns of the Punic Wars.
-
E.
ArabCommander
Indicates that the subject serves as a military commander associated with Arab forces or entities.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: April 29, 2026, 8:20 p.m.