Triple
T23211536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabriel Antonio de Borbón y Sajonia |
E580605
|
entity |
| Predicate | royalHouseRole |
P25666
|
FINISHED |
| Object | younger son of the king |
—
|
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: younger son of the king | Statement: [Gabriel Antonio de Borbón y Sajonia, royalHouseRole, younger son of the king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalHouseRole Context triple: [Gabriel Antonio de Borbón y Sajonia, royalHouseRole, younger son of the king]
-
A.
monarchicalRole
Indicates that one entity holds or is assigned a specific position, function, or office within a monarchical system of governance.
-
B.
royalHouseType
Indicates the specific kind or category of royal house associated with an entity (e.g., dynasty, ruling family type, or royal lineage classification).
-
C.
royalFunction
Indicates a role, duty, or activity specifically associated with royalty or the exercise of royal authority.
-
D.
dynasticRole
chosen
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
E.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191620378819096362252c3b819b6 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.