Triple
T36056749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Politics of Jersey |
E1042966
|
entity |
| Predicate | formerLegislatureName |
P127229
|
FINISHED |
| Object | States of Jersey |
—
|
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: States of Jersey | Statement: [Politics of Jersey, formerLegislatureName, States of Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerLegislatureName Context triple: [Politics of Jersey, formerLegislatureName, States of Jersey]
-
A.
formerLegislatureChambers
Indicates that an entity once served as a legislative chamber but no longer holds that function.
-
B.
previousLegislativeBody
chosen
Indicates that one legislative body directly preceded another in an official sequence or succession.
-
C.
hasLegislatureName
Indicates the formal name assigned to a legislature associated with an entity.
-
D.
correspondingLegislature
Indicates the relationship in which a given political or administrative unit is linked to the specific legislative body that formally represents or governs it.
-
E.
electoralBodyPreviouslyKnownAs
Indicates that an electoral body was formerly known by a different official name before being renamed or reconstituted.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: May 3, 2026, 4:08 p.m.