Triple
T10204472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of Ethiopia |
E238965
|
entity |
| Predicate | laterGoverningSystem |
P92696
|
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: [Emperor of Ethiopia, laterGoverningSystem, constitutional monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterGoverningSystem Context triple: [Emperor of Ethiopia, laterGoverningSystem, constitutional monarchy]
-
A.
laterPoliticalSystemUnderRule
Indicates that one political system came under the rule or authority of another political system at a later point in time.
-
B.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
C.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
-
D.
laterPolicy
Indicates that one policy occurs or becomes effective after another policy in time.
-
E.
governingBodyAfter
Indicates that one governing body succeeds another as the official authority over the same entity or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdeed8644c8190b497aaf52583fa6d |
completed | April 2, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8b7f348190a585daa70de4d4c8 |
completed | April 1, 2026, 8:14 p.m. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:14 p.m.