Triple
T9487611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mediolanum (259) |
E228800
|
entity |
| Predicate | chronologicalOrderInCrisis |
P23880
|
FINISHED |
| Object | mid-3rd-century event |
—
|
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: mid-3rd-century event | Statement: [Battle of Mediolanum (259), chronologicalOrderInCrisis, mid-3rd-century event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalOrderInCrisis Context triple: [Battle of Mediolanum (259), chronologicalOrderInCrisis, mid-3rd-century event]
-
A.
chronologicallyCovers
Indicates that one time period, event, or sequence extends over and includes the entire chronological span of another.
-
B.
chronologicallyFocusesOn
Indicates that something is primarily concerned with or organized around the sequence and progression of events over time.
-
C.
chronologicalOrderInSeries
chosen
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
-
D.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
E.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd80c443b88190968d2092a73e1ee4 |
completed | April 1, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.