Triple
T36219615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nassau-Vianden |
E1047808
|
entity |
| Predicate | partOfDynasticHouse |
P91745
|
FINISHED |
| Object | House of 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 Nassau | Statement: [Nassau-Vianden, partOfDynasticHouse, House of Nassau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfDynasticHouse Context triple: [Nassau-Vianden, partOfDynasticHouse, House of Nassau]
-
A.
partOfDynasty
chosen
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
-
B.
dynasticHouseInvolved
Indicates that a particular dynastic house (royal or noble lineage) is involved in, associated with, or plays a role in the referenced event, entity, or relationship.
-
C.
dynasticBranch
Indicates a genealogical relationship where one lineage or house originates from, or is a subordinate offshoot of, a larger parent dynasty.
-
D.
titleHolderDynasticHouse
Indicates the dynastic house or ruling family that holds a particular title.
-
E.
monarchicalHouse
Indicates that an entity belongs to, is associated with, or is part of a particular royal or monarchical 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
Created at: May 3, 2026, 4:09 p.m.