Triple
T6181246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign |
E137945
|
entity |
| Predicate | exercisesPowerWithin |
P19487
|
FINISHED |
| Object | Constitutional framework |
—
|
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 framework | Statement: [Sovereign, exercisesPowerWithin, Constitutional framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisesPowerWithin Context triple: [Sovereign, exercisesPowerWithin, Constitutional framework]
-
A.
exercisesPowerInNameOf
Indicates that one entity wields authority or influence on behalf of, and under the authorization or representation of, another entity.
-
B.
exerciseOfPower
chosen
Indicates the exertion or application of authority, control, or influence by one entity over another or within a given context.
-
C.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
D.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
E.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c060fdf7ac8190a0e887907ec9a922 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.