Triple
T2847884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omnipotent Government |
E63023
|
entity |
| Predicate | positionOnGovernmentIntervention |
P25259
|
FINISHED |
| Object | critical |
—
|
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: critical | Statement: [Omnipotent Government, positionOnGovernmentIntervention, critical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnGovernmentIntervention Context triple: [Omnipotent Government, positionOnGovernmentIntervention, critical]
-
A.
positionOnGovernment
Indicates an entity’s stance, role, or status within a governmental structure or political office.
-
B.
governmentInvolvement
Indicates that a government participates in, influences, regulates, or otherwise plays a role in the specified activity, process, or entity.
-
C.
positionOnGovernmentRole
Indicates that an entity holds or is assigned to a specific role or office within a government structure.
-
D.
stanceTowardGovernment
chosen
Indicates the attitude, position, or level of support or opposition that an entity holds toward a government.
-
E.
governmentAction
Indicates actions, decisions, or interventions carried out by a government or its agencies in relation to other entities.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf403698819084fb4ace5839aa05 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.