Triple
T4985807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch monarchy |
E111998
|
entity |
| Predicate | typeOfStateHead |
P15442
|
FINISHED |
| Object | hereditary head of state |
—
|
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 head of state | Statement: [Dutch monarchy, typeOfStateHead, hereditary head of state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfStateHead Context triple: [Dutch monarchy, typeOfStateHead, hereditary head of state]
-
A.
typeOfState
chosen
Indicates that one state is a specific kind or category of another, more general state.
-
B.
stateHead
Indicates that one entity serves as the head or leader of a state-level governmental or administrative unit in relation to the other entity.
-
C.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
D.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
E.
governorateType
Indicates the specific classification or category of a governorate within an administrative or governmental hierarchy.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.