Triple
T24346547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolton-le-Moors |
E613655
|
entity |
| Predicate | modernMetropolitanCounty |
P12101
|
FINISHED |
| Object | Greater Manchester |
—
|
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: Greater Manchester | Statement: [Bolton-le-Moors, modernMetropolitanCounty, Greater Manchester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernMetropolitanCounty Context triple: [Bolton-le-Moors, modernMetropolitanCounty, Greater Manchester]
-
A.
metropolitan
Indicates that a location is part of, belongs to, or lies within a specified metropolitan (urban) area.
-
B.
modernCityIs
Indicates that something possesses the characteristics or status of being a modern city.
-
C.
modernLocality
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
-
D.
hasMetropolitanCounty
chosen
Indicates that an entity is associated with, located within, or administered by a specific metropolitan county.
-
E.
centerCityModernName
Indicates that the object is the current or modern name of the city that serves as the center or capital associated with the subject.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932978b88190afc441a3d4805e5f |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.