Triple
T24112131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ynglinga saga |
E597404
|
entity |
| Predicate | featuresDynasty |
P1547
|
FINISHED |
| Object | House of Yngling |
—
|
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: House of Yngling | Statement: [Ynglinga saga, featuresDynasty, House of Yngling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDynasty Context triple: [Ynglinga saga, featuresDynasty, House of Yngling]
-
A.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
-
B.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
-
C.
dynasticLegacy
Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
-
D.
basedOnDynasty
Indicates that something is derived from, influenced by, or established on the foundation of a particular dynasty.
-
E.
dynasty
chosen
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1bd81c8190a44f07487d2ba176 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:03 p.m.