Triple
T36280080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Manchester rail zone |
E892915
|
entity |
| Predicate | centralAreaServed |
P163466
|
FINISHED |
| Object | Manchester city centre |
—
|
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: Manchester city centre | Statement: [Greater Manchester rail zone, centralAreaServed, Manchester city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralAreaServed Context triple: [Greater Manchester rail zone, centralAreaServed, Manchester city centre]
-
A.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
B.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
C.
urbanCenterServed
chosen
Indicates that a particular urban center is provided with services or coverage by a specified entity (such as an infrastructure system, facility, or organization).
-
D.
strategicAreaServed
Indicates that an entity provides services or exerts influence within a particular area considered strategically important.
-
E.
areaOfService
Indicates the geographic or functional region within which a service is provided or applicable.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:09 p.m.