Triple
T22406439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mons Graupius |
E553890
|
entity |
| Predicate | belligerentForce |
P39448
|
FINISHED |
| Object | Roman legions |
—
|
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: Roman legions | Statement: [Battle of Mons Graupius, belligerentForce, Roman legions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belligerentForce Context triple: [Battle of Mons Graupius, belligerentForce, Roman legions]
-
A.
stateOfForces
Indicates the condition, disposition, or readiness level of military or organizational forces at a given time.
-
B.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
C.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
-
D.
isPrimaryLandForceOf
Indicates that a military land force serves as the main or principal ground combat component of a specified country, alliance, or organization.
-
E.
armedForcesInvolved
chosen
Indicates that the relationship or event involves the participation or presence of military or armed forces.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b835e88190a388e19577df771e |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.