Triple
T1739443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolton |
E38197
|
entity |
| Predicate | previousAdministrativeStatus |
P14579
|
FINISHED |
| Object | municipal borough in Lancashire |
—
|
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: municipal borough in Lancashire | Statement: [Bolton, previousAdministrativeStatus, municipal borough in Lancashire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAdministrativeStatus Context triple: [Bolton, previousAdministrativeStatus, municipal borough in Lancashire]
-
A.
formerAdministrativeStatus
chosen
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
B.
previousAdministrator
Indicates that one entity formerly held an administrative role or position over another entity before the current administrator.
-
C.
earlierStatus
Indicates that one status or condition occurred or was valid before another status in time.
-
D.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
E.
formerAdministeredBy
Indicates that an entity was previously administered or managed by another entity, but is no longer under that administration.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.