Triple
T27146681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayoress of Arnhem |
E681968
|
entity |
| Predicate | hasNoStatutoryPowers |
P196415
|
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: [Mayoress of Arnhem, hasNoStatutoryPowers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoStatutoryPowers Context triple: [Mayoress of Arnhem, hasNoStatutoryPowers, true]
-
A.
hasNoConstitutionalPowers
Indicates that the subject entity lacks any powers or authorities granted or defined by a constitution.
-
B.
hasNoLegislativePower
Indicates that the referenced entity lacks any authority or capacity to create, amend, or enact laws or binding legislative rules.
-
C.
hasNoExecutivePower
Indicates that the subject holds a position or role that does not include authority to make or enforce executive decisions.
-
D.
hasRegulatoryPower
Indicates that one entity possesses formal authority to create, enforce, or oversee rules and regulations governing another entity or activity.
-
E.
hasNoLegalAuthority
Indicates that an entity lacks the official power, right, or authorization to perform a specified action or make binding decisions in a given context.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
| PDg | Predicate description generation | batch_69fe349739cc8190a21c408208312e6c |
completed | May 8, 2026, 7:08 p.m. |
Created at: April 27, 2026, 9:11 a.m.