Triple
T383568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reform Act 1832 |
E8730
|
entity |
| Predicate | redistributedSeatsTo |
P1682
|
FINISHED |
| Object | industrial towns |
—
|
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: industrial towns | Statement: [Reform Act 1832, redistributedSeatsTo, industrial towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redistributedSeatsTo Context triple: [Reform Act 1832, redistributedSeatsTo, industrial towns]
-
A.
apportionedBy
chosen
Indicates that something is divided or allocated among parts or recipients according to a specified agent, rule, or method.
-
B.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
C.
governanceChange
Indicates a change in the structure, rules, or authority of how an entity, organization, or system is governed.
-
D.
divisionRealignment
Indicates a reorganization of how entities are grouped into divisions, typically involving changes to which entities belong to which division.
-
E.
hasRedistrictingProcess
Indicates that an entity is subject to, or participates in, a defined process for redrawing electoral or administrative district boundaries.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec40ff8c81909306eb2dfe1512af |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96602188190b0cbc167f55a9237 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.