Triple
T37009481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Capua |
E915898
|
entity |
| Predicate | RomanStrategy |
P47691
|
FINISHED |
| Object | Refusal to be drawn away from siege works |
—
|
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: Refusal to be drawn away from siege works | Statement: [Battle of Capua, RomanStrategy, Refusal to be drawn away from siege works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanStrategy Context triple: [Battle of Capua, RomanStrategy, Refusal to be drawn away from siege works]
-
A.
RomanVictory
Indicates that the Romans achieved a successful military outcome over their opponents.
-
B.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
C.
RomanCommander
Indicates a relationship where an entity holds the role or position of a commander within a Roman military or organizational context.
-
D.
SamniteCommander
Indicates that one entity serves as a military commander or leader within the Samnite forces or context.
-
E.
aimOfRome
chosen
Indicates that something is the goal, purpose, or intended objective of Rome.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.