Triple
T19583579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolt in 2100 |
E490053
|
entity |
| Predicate | featuresGovernmentType |
P136350
|
FINISHED |
| Object | theocracy |
—
|
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: theocracy | Statement: [Revolt in 2100, featuresGovernmentType, theocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGovernmentType Context triple: [Revolt in 2100, featuresGovernmentType, theocracy]
-
A.
targetGovernmentType
Indicates the form or system of governance that an entity is directed toward, associated with, or intended to influence.
-
B.
typeOfGovernmentInstitution
Indicates that one entity is a government institution of the type or category specified by the other entity.
-
C.
typeOfGovernmentCenter
Indicates the specific form or classification of governmental authority that a particular administrative center serves or represents.
-
D.
governmentTypeServed
Indicates the type of government that an entity serves, is affiliated with, or operates under in its role or function.
-
E.
governmentBodyType
Indicates the classification or category of a governmental organization based on its structural or functional role.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6404f34b081908aeb9cc9a5ddf539 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:42 p.m.