Triple
T18845798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C6 |
E460908
|
entity |
| Predicate | hasNoLegislativePower |
P133160
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [C6, hasNoLegislativePower, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoLegislativePower Context triple: [C6, hasNoLegislativePower, true]
-
A.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
B.
excludesFromLegislativePower
Indicates that one entity is not subject to, or is placed outside the scope of, another entity’s authority to create or apply legislation.
-
C.
hasNoFormalConstitutionalStatus
Indicates that the entity lacks any officially recognized status or role within a formal constitutional framework.
-
D.
cannotLegislateOn
Indicates that one entity lacks the authority or legal power to create, modify, or enact laws concerning a specified subject, domain, or other entity.
-
E.
hasConcurrentLegislativePowers
Indicates that two or more governing bodies share the authority to legislate on the same subject matter at the same time.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ee96988190bf247b986777945c |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.