Triple
T36582461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernestine line |
E902430
|
entity |
| Predicate | producedRoyalHouse |
P199008
|
FINISHED |
| Object | House of Saxe-Coburg and Gotha |
—
|
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 Saxe-Coburg and Gotha | Statement: [Ernestine line, producedRoyalHouse, House of Saxe-Coburg and Gotha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedRoyalHouse Context triple: [Ernestine line, producedRoyalHouse, House of Saxe-Coburg and Gotha]
-
A.
relatedRoyalHouse
Indicates a relationship where one royal house is historically, genealogically, or politically connected to another royal house.
-
B.
lastRoyalHouseOf
Indicates that one entity is the final ruling royal house or dynasty associated with another entity, such as a realm, title, or political unit.
-
C.
reigningRoyalHouseOf
Indicates that a particular royal house currently holds the ruling monarchy over a specified realm or country.
-
D.
notableRoyalHouse
Indicates that an entity is prominently associated with, or belongs to, a particular royal house or dynasty.
-
E.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
| PDg | Predicate description generation | batch_69ff1a95b6fc81909331bb03e263b5b9 |
completed | May 9, 2026, 11:29 a.m. |
Created at: May 3, 2026, 4:11 p.m.