Triple
T28660810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Hispania |
E725461
|
entity |
| Predicate | sufferedInvasionBy |
P21625
|
FINISHED |
| Object | Vandals |
—
|
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: Vandals | Statement: [Diocese of Hispania, sufferedInvasionBy, Vandals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedInvasionBy Context triple: [Diocese of Hispania, sufferedInvasionBy, Vandals]
-
A.
wasInvadedBy
chosen
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
B.
invasionDate
Indicates the date on which an invasion event occurred or began.
-
C.
invasionAddressed
Indicates that an invasion event has been responded to or dealt with through some form of action, intervention, or resolution.
-
D.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
E.
invasionEndDate
Indicates the date on which an invasion event is considered to have ended.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:58 a.m.