Triple
T33990878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reading Borough Police |
E871538
|
entity |
| Predicate | operatedWithinLegalSystem |
P131132
|
FINISHED |
| Object | English law |
—
|
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: English law | Statement: [Reading Borough Police, operatedWithinLegalSystem, English law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedWithinLegalSystem Context triple: [Reading Borough Police, operatedWithinLegalSystem, English law]
-
A.
usedLegalSystemOf
chosen
Indicates that one entity applied, followed, or operated under the legal system or body of laws belonging to another entity.
-
B.
governedByLegalRegime
Indicates that an entity is subject to, regulated by, or operating under a specific legal framework or set of legal rules.
-
C.
hasLegalSystemType
Indicates that an entity possesses or is governed by a particular type or form of legal system.
-
D.
legalSystemWorkedIn
Indicates that a person carried out their professional legal activities within a particular legal system or jurisdiction.
-
E.
legalSystemOverseen
Indicates that one entity has authority to supervise, administer, or control the operation of a particular legal system.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: May 1, 2026, 1:50 a.m.