Triple
T3905888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 1952 (Greece) |
E87203
|
entity |
| Predicate | definedStateForm |
P35007
|
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: [Constitution of 1952 (Greece), definedStateForm, hereditary monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedStateForm Context triple: [Constitution of 1952 (Greece), definedStateForm, hereditary monarchy]
-
A.
stateForm
chosen
Indicates that an entity has the political or constitutional form of a particular state or system of government.
-
B.
supportsFormOfState
Indicates that one entity endorses, upholds, or favors a particular form or system of state governance associated with another entity.
-
C.
formedInState
Indicates that an entity was created, established, or officially organized within a particular state or subnational jurisdiction.
-
D.
statesBoundOfForm
Indicates that one state or condition serves as a boundary or limiting form for another.
-
E.
formerState
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.