Triple
T15462053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nubian campaign of Ramesses II |
E371925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian military expedition |
C34219
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ancient Egyptian military expedition Context triple: [Nubian campaign of Ramesses II, instanceOf, ancient Egyptian military expedition]
-
A.
Mir expedition
The Mir expedition class represents a long-duration crewed mission to the Mir space station, encompassing its objectives, crew, timeline, activities, and outcomes.
-
B.
Carthaginian military operation
A Carthaginian military operation is a coordinated campaign or action conducted by Carthage’s armed forces, typically involving naval and land components, to achieve strategic, political, or economic objectives.
-
C.
United States Army expedition
A United States Army expedition is a formally organized, often temporary military operation conducted by the U.S. Army beyond its usual garrison locations to achieve specific strategic, tactical, or exploratory objectives.
-
D.
papal military campaign
A papal military campaign is an organized armed expedition initiated, sanctioned, or led by the pope or the Papal States to pursue religious, political, or territorial objectives.
-
E.
ancient Near Eastern war
chosen
Ancient Near Eastern war encompasses the organized, often ritualized conflicts between early civilizations of Mesopotamia, Egypt, Anatolia, and the Levant, characterized by chariot warfare, fortified cities, imperial expansion, and the intertwining of military action with religion and kingship.
- F. None of above.
Provenance (1 batch)
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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:32 a.m.