Triple
T8322939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wansdyke District Council |
E194877
|
entity |
| Predicate | operatedInLegalSystem |
P57899
|
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: [Wansdyke District Council, operatedInLegalSystem, English law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInLegalSystem Context triple: [Wansdyke District Council, operatedInLegalSystem, English law]
-
A.
legalSystemWorkedIn
Indicates that a person carried out their professional legal activities within a particular legal system or jurisdiction.
-
B.
partOfLegalSystem
chosen
Indicates that something belongs to, is included within, or functions as a component of a particular legal system.
-
C.
legalSystemWorkedOn
Indicates that a legal system has been applied to, influenced, or modified by some agent or process.
-
D.
legalSystem
Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
-
E.
hasLegalSystemType
Indicates that an entity possesses or is governed by a particular type or form of 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f7cf49c8190b8440ff01926a66a |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.