Triple
T586969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nepal |
E15177
|
entity |
| Predicate | formerGovernmentType |
P220
|
FINISHED |
| Object | constitutional 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: constitutional monarchy | Statement: [Nepal, formerGovernmentType, constitutional monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerGovernmentType Context triple: [Nepal, formerGovernmentType, constitutional monarchy]
-
A.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
B.
formerPoliticalEntity
Indicates that an entity was once a political entity (such as a state, country, or polity) but no longer exists in that political form.
-
C.
formerDesignation
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
D.
formedGovernmentIn
Indicates that an entity established or took office as the governing authority of a political unit in a specified place or jurisdiction.
-
E.
formerDirector
Indicates that one entity previously held the position of director of the other entity but no longer does.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9bf0cc8190a145ccd6fc501349 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494ca68448190a516b9c3525d8916 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.