Triple
T15207242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anscar I of Ivrea |
E363419
|
entity |
| Predicate | dynastyFoundedBecame |
P117123
|
FINISHED |
| Object | royal house in Italy |
—
|
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: royal house in Italy | Statement: [Anscar I of Ivrea, dynastyFoundedBecame, royal house in Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyFoundedBecame Context triple: [Anscar I of Ivrea, dynastyFoundedBecame, royal house in Italy]
-
A.
dynastyFoundedByMember
Indicates that a dynasty was established or initiated by a specific individual who is a member of that dynasty.
-
B.
hasDynastyFounded
Indicates that an entity is the founder or originator of a particular dynasty.
-
C.
foundingDynastyOf
Indicates that a particular dynasty is the original founding ruling house or lineage of a specified political entity, state, or realm.
-
D.
founderDynasty
Indicates that an entity is the founding member or originator of a particular dynasty.
-
E.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b8e2788190bd1831762e4181ae |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:11 a.m.