Triple
T26430278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legislative Assembly of Amapá |
E664485
|
entity |
| Predicate | hasLegislativePowerLevel |
P166876
|
FINISHED |
| Object | state |
—
|
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: state | Statement: [Legislative Assembly of Amapá, hasLegislativePowerLevel, state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegislativePowerLevel Context triple: [Legislative Assembly of Amapá, hasLegislativePowerLevel, state]
-
A.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
B.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
C.
legislativePowerScope
chosen
Indicates the range or extent of authority that a legislative body has to create, amend, or repeal laws.
-
D.
hasLegislativeType
Indicates that something is associated with, classified by, or characterized as a particular type or category of legislation or legislative measure.
-
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.
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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 26, 2026, 11:48 p.m.