Triple
T29103790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amal dynasty |
E736706
|
entity |
| Predicate | includesRoyalWoman |
P139262
|
FINISHED |
| Object | Amalasuintha |
—
|
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: Amalasuintha | Statement: [Amal dynasty, includesRoyalWoman, Amalasuintha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRoyalWoman Context triple: [Amal dynasty, includesRoyalWoman, Amalasuintha]
-
A.
royalMistressOf
Indicates that one person is the (typically unofficial) romantic or sexual partner of a royal figure, such as a king or prince.
-
B.
hasRoyalFavourite
Indicates that one entity is the person specially favored or preferred by a royal figure.
-
C.
royalHouseAsQueen
chosen
Indicates that a person serves or has served as queen within a specified royal house or dynasty.
-
D.
managerOfRoyals
Indicates that one entity serves as the manager responsible for overseeing or directing the Royals.
-
E.
princessOf
Indicates that one entity holds the royal title or role of princess in relation to another entity, typically a realm, family, or sovereign.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: April 28, 2026, 11:14 a.m.