Triple
T2154098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Manchester Zone 4 |
E47846
|
entity |
| Predicate | zoneType |
P36294
|
FINISHED |
| Object | outer zone |
—
|
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: outer zone | Statement: [Greater Manchester Zone 4, zoneType, outer zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneType Context triple: [Greater Manchester Zone 4, zoneType, outer zone]
-
A.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
B.
timeZoneType
Indicates the classification or category of a time zone associated with an entity (e.g., standard, daylight, or specific time zone format/type).
-
C.
zoneConcept
Indicates that one entity is associated with, defined by, or operates within a particular zone or conceptual area specified by another entity.
-
D.
timeZoneRegionType
Indicates the classification of a time zone based on the type of geographic or administrative region it is associated with.
-
E.
timeZoneDesignation
Indicates the specific time zone label or code assigned to an entity for representing its local time.
- F. None of above. chosen
Provenance (4 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe64fdf081909a5ea6818bddd18c |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:44 p.m.