Triple
T10682753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham PlusBus area |
E251796
|
entity |
| Predicate | isUrbanZoneFor |
P95295
|
FINISHED |
| Object | Nottingham PlusBus tickets |
—
|
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: Nottingham PlusBus tickets | Statement: [Nottingham PlusBus area, isUrbanZoneFor, Nottingham PlusBus tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanZoneFor Context triple: [Nottingham PlusBus area, isUrbanZoneFor, Nottingham PlusBus tickets]
-
A.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
B.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
-
C.
hasUrbanDistrictFunction
Indicates that an entity serves the administrative or functional role of an urban district within a larger territorial or governance structure.
-
D.
isUrbanizedAround
Indicates that an area or region has developed urban characteristics or infrastructure surrounding a particular location or feature.
-
E.
hasUrbanClassification
Indicates that an entity is assigned a specific urban status or category within a defined classification system.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc43b9481908f35490db93db76c |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:10 p.m.