Triple
T9088875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kadesh |
E217826
|
entity |
| Predicate | approximateEgyptianForces |
P65494
|
FINISHED |
| Object | c. 20,000 soldiers |
—
|
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. 20,000 soldiers | Statement: [Battle of Kadesh, approximateEgyptianForces, c. 20,000 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateEgyptianForces Context triple: [Battle of Kadesh, approximateEgyptianForces, c. 20,000 soldiers]
-
A.
combatantStrengthEgyptian
chosen
Indicates that the entity has combatant strength or military capability associated with Egyptian forces or context.
-
B.
opponentAtBattleOfTheNile
Indicates that one entity was an opposing combatant of the other in the Battle of the Nile.
-
C.
estimatedCarthaginianForces
Indicates an assessment or approximation of the size or strength of the military forces associated with Carthage.
-
D.
attackingForceApprox
Indicates that one entity is the approximate attacking force, in terms of size or strength, relative to another entity or context.
-
E.
estimatedRomanForces
Indicates that a specified quantity represents an estimate of the size or strength of Roman military forces involved in a particular context or event.
- 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.