Triple
T32547160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Isonzo (489) |
E831875
|
entity |
| Predicate | primaryVictoriousRuler |
P206306
|
FINISHED |
| Object | Theodoric the Great |
E200342
|
NE 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: Theodoric the Great | Statement: [Battle of Isonzo (489), primaryVictoriousRuler, Theodoric the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVictoriousRuler Context triple: [Battle of Isonzo (489), primaryVictoriousRuler, Theodoric the Great]
-
A.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
B.
historicalRulers
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
C.
associatedDynastyRuler
Indicates a relationship where a dynasty is linked to the ruler who governed or is historically connected with it.
-
D.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
-
E.
hasFamousRuler
Indicates that an entity is or was ruled by a ruler who is widely recognized or historically notable.
- F. None of above. chosen
Provenance (5 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a352f9a277881908c911c0c5f65b8f4 |
completed | June 19, 2026, 12:01 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:02 a.m.