Triple
T16509364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford, Sefton |
E401015
|
entity |
| Predicate | hasSuburbType |
P36805
|
FINISHED |
| Object | suburb of Liverpool |
—
|
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: suburb of Liverpool | Statement: [Ford, Sefton, hasSuburbType, suburb of Liverpool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuburbType Context triple: [Ford, Sefton, hasSuburbType, suburb of Liverpool]
-
A.
hasTypeOfSubdivision
chosen
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
B.
containsSuburbs
Indicates that a larger geographic area or administrative region includes one or more suburbs within its boundaries.
-
C.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
-
D.
hasSuburbAlong
Indicates that a larger area or route is associated with, or passes by, one or more suburbs located along its extent.
-
E.
hasMajorSuburb
Indicates that a larger urban area includes or is associated with a specific major suburb within its boundaries or sphere.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e54f7508190804bbae4c9bc8fe3 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.