Triple
T23863362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Parma (consort) |
E592509
|
entity |
| Predicate | titleHolderRoyalHouseByBirth |
P72476
|
FINISHED |
| Object | House of Orange-Nassau |
—
|
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 Orange-Nassau | Statement: [Duchess of Parma (consort), titleHolderRoyalHouseByBirth, House of Orange-Nassau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderRoyalHouseByBirth Context triple: [Duchess of Parma (consort), titleHolderRoyalHouseByBirth, House of Orange-Nassau]
-
A.
titleHolderDynasticHouse
chosen
Indicates the dynastic house or ruling family that holds a particular title.
-
B.
reigningRoyalHouseOf
Indicates that a particular royal house currently holds the ruling monarchy over a specified realm or country.
-
C.
royalAssociation
Indicates a relationship in which an entity is connected or linked to royalty, a royal person, or a royal institution.
-
D.
notableRoyalHouse
Indicates that an entity is prominently associated with, or belongs to, a particular royal house or dynasty.
-
E.
dateOfBirthOfChildRoyalReign
Indicates the specific date on which a child was born during a particular royal’s reign.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae16df4819081a8b3a395e45118 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.