Triple
T32209904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of the Visigoths |
E822768
|
entity |
| Predicate | noblePowerBase |
P174981
|
FINISHED |
| Object | Visigothic aristocracy |
—
|
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: Visigothic aristocracy | Statement: [King of the Visigoths, noblePowerBase, Visigothic aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noblePowerBase Context triple: [King of the Visigoths, noblePowerBase, Visigothic aristocracy]
-
A.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
B.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
C.
usesNoblePhantasm
Indicates that an entity activates or employs a Noble Phantasm as part of an action or event.
-
D.
heroPower
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
E.
powerCharacter
Indicates that one entity possesses, controls, or exerts power or influence over another entity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 12:37 a.m.