Triple
T8772723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Verona (402) |
E208501
|
entity |
| Predicate | chronologyWithinInvasion |
P26528
|
FINISHED |
| Object | final major engagement of Alaric I's 401–402 Italian campaign |
—
|
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: final major engagement of Alaric I's 401–402 Italian campaign | Statement: [Battle of Verona (402), chronologyWithinInvasion, final major engagement of Alaric I's 401–402 Italian campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyWithinInvasion Context triple: [Battle of Verona (402), chronologyWithinInvasion, final major engagement of Alaric I's 401–402 Italian campaign]
-
A.
chronologyWithinConflict
chosen
Indicates that one event or time period occurs within the temporal span of a specified conflict or war.
-
B.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
C.
chronologyWithinRevolution
Indicates that one event or time period occurs within the temporal span of a specified revolution.
-
D.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
E.
chronologyStart
Indicates the point in time at which a sequence, event, or temporal record begins.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2dc87c8190be0597a260d95a0b |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.