Triple
T30551263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amun division |
E777564
|
entity |
| Predicate | approximateDateOfBattleOfKadeshParticipation |
P185194
|
FINISHED |
| Object | c. 1274 BCE |
—
|
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: c. 1274 BCE | Statement: [Amun division, approximateDateOfBattleOfKadeshParticipation, c. 1274 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfBattleOfKadeshParticipation Context triple: [Amun division, approximateDateOfBattleOfKadeshParticipation, c. 1274 BCE]
-
A.
sideInBattleOfYarmouk
Indicates that an entity participated as a side (belligerent) in the Battle of Yarmouk.
-
B.
opponentInBattleOfGeokTepe
Indicates that two parties were opposing sides against each other in the Battle of Geok Tepe.
-
C.
approximateBattleDate
chosen
Indicates that the associated date is an estimated or approximate time when the battle occurred, rather than an exact, confirmed date.
-
D.
opponentAtBattleOfTheNile
Indicates that one entity was an opposing combatant of the other in the Battle of the Nile.
-
E.
battleParticipated
Indicates that an entity took part in a specific battle as a combatant or participant.
- 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_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 29, 2026, 8:20 p.m.