Triple
T18116889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio IX Hispana |
E433626
|
entity |
| Predicate | possiblyDestroyedIn |
P130508
|
FINISHED |
| Object | northern Britain |
—
|
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: northern Britain | Statement: [Legio IX Hispana, possiblyDestroyedIn, northern Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possiblyDestroyedIn Context triple: [Legio IX Hispana, possiblyDestroyedIn, northern Britain]
-
A.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
B.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
C.
wasDestroyedOrTransformed
Indicates that an entity ceased to exist in its original form due to being either destroyed or fundamentally transformed.
-
D.
destroyedInConflictWith
Indicates that one entity was destroyed as a direct result of a conflict or confrontation with another entity.
-
E.
destroyedMultipleTimes
Indicates that the same entity has been destroyed on more than one distinct occasion.
- F. None of above. chosen
Provenance (4 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd67a2481909d27a4a49b095f8c |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.