Triple
T13603789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faulkner Act mayor–council |
E325007
|
entity |
| Predicate | legislativePowersVestedIn |
P2844
|
FINISHED |
| Object | council |
—
|
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: council | Statement: [Faulkner Act mayor–council, legislativePowersVestedIn, council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativePowersVestedIn Context triple: [Faulkner Act mayor–council, legislativePowersVestedIn, council]
-
A.
legislativePowersDerivedFrom
Indicates that an entity’s authority to make or enact laws originates from, or is granted by, another specified source.
-
B.
hasLegislativePower
chosen
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
C.
constitutionalPower
Indicates that an entity holds authority or rights granted and defined by a constitution in relation to another entity or domain of action.
-
D.
legislativeBase
Indicates that one entity serves as the legal or legislative basis, authority, or foundation for another entity or action.
-
E.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.