Triple
T290553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orpington |
E5981
|
entity |
| Predicate | isResidentialHubIn |
P9421
|
FINISHED |
| Object | southeast Greater London |
—
|
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: southeast Greater London | Statement: [Orpington, isResidentialHubIn, southeast Greater London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResidentialHubIn Context triple: [Orpington, isResidentialHubIn, southeast Greater London]
-
A.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
-
B.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
C.
hasTransportHub
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
-
D.
isHomeOf
Indicates that a place serves as the primary residence or base for a person, group, or organization.
-
E.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4f78bc81909a64fd6aaec3b504 |
completed | Feb. 28, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69a25b7d089081909810442c3d0182f6 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25d0ec71081908478c800be4f7bb0 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.