Triple
T20317810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Ducal estates of Luxembourg |
E492125
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal estates |
C42810
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: royal estates Context triple: [Grand Ducal estates of Luxembourg, instanceOf, royal estates]
-
A.
royal hunting estate
A royal hunting estate is a large, often secluded tract of land reserved for a monarch and their court, combining managed wilderness, game populations, and supporting facilities for exclusive hunting, leisure, and display of power.
-
B.
imperial estate
An imperial estate is a large, centrally administered landholding owned or controlled by an emperor or imperial authority, typically encompassing agricultural, residential, and administrative functions that support the imperial household and governance.
-
C.
royal domain
chosen
A royal domain is a territory or collection of lands directly owned, controlled, and administered by a monarch as part of the crown’s personal or sovereign holdings.
-
D.
estate of the realm
An estate of the realm is a broad social or political order—such as clergy, nobility, or commoners—recognized in a traditional hierarchical structure of governance and representation.
-
E.
royal house
A royal house is a dynastic family line that holds or has held a hereditary monarchy, encompassing its members, titles, traditions, and political influence over time.
- F. None of above.
Provenance (1 batch)
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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:20 a.m.