Triple
T36248121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N postcode area |
E891719
|
entity |
| Predicate | coversNeighbourhood |
P141690
|
FINISHED |
| Object | Islington |
—
|
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: Islington | Statement: [N postcode area, coversNeighbourhood, Islington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversNeighbourhood Context triple: [N postcode area, coversNeighbourhood, Islington]
-
A.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
B.
coversLocality
chosen
Indicates that one entity spatially includes or encompasses the area or extent of a specified locality.
-
C.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
D.
occurredInNeighborhood
Indicates that an event or action took place within the boundaries of a specific neighborhood.
-
E.
coversCity
Indicates that one entity extends over, includes, or geographically encompasses the area of a specified city.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:09 p.m.