Triple
T4697955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20 Fenchurch Street |
E104194
|
entity |
| Predicate | locatedInFinancialDistrict |
P40
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [20 Fenchurch Street, locatedInFinancialDistrict, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFinancialDistrict Context triple: [20 Fenchurch Street, locatedInFinancialDistrict, true]
-
A.
hasFinancialDistrict
Indicates that a place or city contains a designated area primarily devoted to financial and banking activities.
-
B.
locatedInSkyscraper
Indicates that one entity is physically situated within or inside a skyscraper.
-
C.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
isInBusinessDistrict
Indicates that an entity is located within a designated business or commercial district area.
-
E.
locatedInDiplomaticQuarter
Indicates that something is situated within an area designated as a diplomatic quarter, typically a district hosting embassies and diplomatic missions.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.