Triple
T30883982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio XVIII |
E786704
|
entity |
| Predicate | destroyedTogetherWith |
P46030
|
FINISHED |
| Object | Legio XVII |
—
|
NE NERFINISHED |
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: Legio XVII | Statement: [Legio XVIII, destroyedTogetherWith, Legio XVII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedTogetherWith Context triple: [Legio XVIII, destroyedTogetherWith, Legio XVII]
-
A.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
B.
killedAlongWith
chosen
Indicates that one entity was killed at the same time and in the same event or circumstance as another entity.
-
C.
destroyedInConflictWith
Indicates that one entity was destroyed as a direct result of a conflict or confrontation with another entity.
-
D.
dissolvedAlongWith
Indicates that one entity ceased to exist, function, or operate at the same time and in conjunction with another entity.
-
E.
sunkTogetherWith
Indicates that one entity sank at the same time and in the same event as another entity.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69204be748190a6a2a401d81c1218 |
completed | May 3, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:48 p.m.