Triple
T24689977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reuss |
E611406
|
entity |
| Predicate | rulingHouseIn |
P9023
|
FINISHED |
| Object | Thuringian states |
—
|
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: Thuringian states | Statement: [Reuss, rulingHouseIn, Thuringian states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingHouseIn Context triple: [Reuss, rulingHouseIn, Thuringian states]
-
A.
rulingHouse
chosen
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.
monarchicalHouse
Indicates that an entity belongs to, is associated with, or is part of a particular royal or monarchical 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.
reigningRoyalHouseOf
Indicates that a particular royal house currently holds the ruling monarchy over a specified realm or country.
-
E.
formerRulerHouse
Indicates that a person once ruled on behalf of, or as a member of, a particular ruling house or dynasty but no longer holds that ruling position.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:20 a.m.