Triple
T12523009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Teti |
E299364
|
entity |
| Predicate | royalHouseType |
P105693
|
FINISHED |
| Object | hereditary monarchy |
—
|
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: hereditary monarchy | Statement: [House of Teti, royalHouseType, hereditary monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalHouseType Context triple: [House of Teti, royalHouseType, hereditary monarchy]
-
A.
rulingHouse
Indicates that one entity serves as the dynastic or noble family that holds ruling authority over another entity, such as a state, territory, or polity.
-
B.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
C.
crownedMonarchHouse
Indicates that a particular royal house is the one from which a given monarch was crowned or to which that crowned monarch belongs.
-
D.
relatedRoyalHouse
Indicates a relationship where one royal house is historically, genealogically, or politically connected to another royal house.
-
E.
reigningRoyalHouseOf
Indicates that a particular royal house currently holds the ruling monarchy over a specified realm or country.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95f5148948190946a575d812b329d |
completed | April 10, 2026, 8:36 p.m. |
Created at: April 8, 2026, 9:57 p.m.