Triple
T3720466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galilean campaign of Vespasian |
E81625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman military operation |
C11928
|
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: Roman military operation Context triple: [Galilean campaign of Vespasian, instanceOf, Roman military operation]
-
A.
Roman military campaign
chosen
A Roman military campaign is a coordinated series of operations conducted by Roman forces, combining strategic planning, logistics, and battlefield tactics to achieve political, territorial, or defensive objectives.
-
B.
Roman military equipment
Roman military equipment encompasses the standardized weapons, armor, tools, and gear used by Roman soldiers to ensure effectiveness, discipline, and adaptability in warfare across the empire.
-
C.
military operation
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
D.
Roman military commander
A Roman military commander is a high-ranking officer responsible for leading legions, planning and executing campaigns, maintaining discipline, and securing Rome’s political and territorial interests through organized warfare.
-
E.
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.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.