Triple
T32119804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NW5 postcode area |
E820336
|
entity |
| Predicate | containsPartOfNeighbourhood |
P135266
|
FINISHED |
| Object | Tufnell Park |
—
|
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: Tufnell Park | Statement: [NW5 postcode area, containsPartOfNeighbourhood, Tufnell Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPartOfNeighbourhood Context triple: [NW5 postcode area, containsPartOfNeighbourhood, Tufnell Park]
-
A.
isPartOfNeighborhoodArea
Indicates that one area or unit is contained within or belongs to a specific neighborhood area.
-
B.
hasNeighborhoodPart
chosen
Indicates that one entity is a spatially adjacent or locally contained part of another entity, typically within its surrounding neighborhood or vicinity.
-
C.
partOfNeighborhoodNetwork
Indicates that an entity belongs to, or is included within, a specific neighborhood’s interconnected network or system.
-
D.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
E.
originatedInNeighborhood
Indicates that an entity began, was founded, or first came into existence within a specific neighborhood.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: May 1, 2026, 12:28 a.m.