Triple
T36678234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Constables |
E905602
|
entity |
| Predicate | hasFullPolicePowers |
P55637
|
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: [Special Constables, hasFullPolicePowers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFullPolicePowers Context triple: [Special Constables, hasFullPolicePowers, true]
-
A.
lawEnforcementPowers
chosen
Indicates that an entity possesses official authority and legal powers to enforce laws, maintain public order, and carry out related policing actions.
-
B.
hasOwnPoliceForce
Indicates that an entity maintains and controls its own dedicated police force or law enforcement agency.
-
C.
hasStatePowers
Indicates that an entity possesses or exercises the official powers or authorities of a state-level government.
-
D.
hasMunicipalityWithExtendedPowers
Indicates that an administrative unit is associated with a municipality that has extended self-governing or administrative powers beyond those of ordinary municipalities.
-
E.
hasPublicAuthority
Indicates that an entity possesses official power or legal authority to act on behalf of the public or a governing body.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7a487408190b3a5ee144e651046 |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.