Triple
T31064744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasdingi |
E791635
|
entity |
| Predicate | notableRulerDynasty |
P147952
|
FINISHED |
| Object | Hasdingian royal line |
E797188
|
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: Hasdingian royal line | Statement: [Hasdingi, notableRulerDynasty, Hasdingian royal line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRulerDynasty Context triple: [Hasdingi, notableRulerDynasty, Hasdingian royal line]
-
A.
associatedDynastyRuler
chosen
Indicates a relationship where a dynasty is linked to the ruler who governed or is historically connected with it.
-
B.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
C.
historicalRulers
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
D.
hasFamousRuler
Indicates that an entity is or was ruled by a ruler who is widely recognized or historically notable.
-
E.
dynastyRuled
Indicates that a particular dynasty held ruling authority or governance over a specified region, state, or people during a certain period.
- F. None of above.
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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a292b1849508190814aff1942097066 |
completed | June 10, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:01 p.m.