Triple
T36910779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Street Roundabout |
E912898
|
entity |
| Predicate | inBusinessDistrict |
P16988
|
FINISHED |
| Object | Tech City |
—
|
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: Tech City | Statement: [Old Street Roundabout, inBusinessDistrict, Tech City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inBusinessDistrict Context triple: [Old Street Roundabout, inBusinessDistrict, Tech City]
-
A.
isInBusinessDistrict
chosen
Indicates that an entity is located within a designated business or commercial district area.
-
B.
hasBusinessDistrict
Indicates that a place or administrative area contains or includes a designated business district within its boundaries.
-
C.
isPartOfBusinessArea
Indicates that one entity belongs to, is included within, or falls under the scope of a particular business area.
-
D.
commercialArea
Indicates that the location or region is designated primarily for commercial activities such as businesses, shops, or services.
-
E.
inCityDistrict
Indicates that one entity is located within the boundaries of a specific city district.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb557f28008190bc684cfb252e0c72 |
completed | May 6, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.