Triple
T34646122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westminster II |
E889698
|
entity |
| Predicate | hasLocationOfEnactment |
P2108
|
FINISHED |
| Object | Westminster |
—
|
NE NERFINISHED |
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: Westminster | Statement: [Westminster II, hasLocationOfEnactment, Westminster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationOfEnactment Context triple: [Westminster II, hasLocationOfEnactment, Westminster]
-
A.
placeOfEnactment
chosen
Indicates the location where an event, action, or legal act is formally carried out or put into effect.
-
B.
intendedJurisdiction
Indicates the legal or geographic area over which something (such as a law, policy, or authority) is meant to have power or apply.
-
C.
associatedLawProclaimedAt
Indicates the date, time, or event at which a particular law or legal act was formally proclaimed or officially announced.
-
D.
existsInJurisdiction
Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
-
E.
jurisdictionOfProsecution
Indicates the legal authority or territory within which a prosecution is carried out or has the power to proceed.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 1, 2026, 2:04 a.m.