Triple
T27299085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Circus |
E688848
|
entity |
| Predicate | locatedNearDistrict |
P197841
|
FINISHED |
| Object | Theatreland, London |
—
|
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: Theatreland, London | Statement: [Cambridge Circus, locatedNearDistrict, Theatreland, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearDistrict Context triple: [Cambridge Circus, locatedNearDistrict, Theatreland, London]
-
A.
locatedNearGovernmentDistrict
Indicates that one entity is situated close to or in the immediate vicinity of a government district.
-
B.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
-
C.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
-
D.
isLocatedInDistrictKnownFor
Indicates that an entity is situated within a district that is notably recognized for a particular characteristic, feature, or reputation.
-
E.
birthPlaceDistrict
Indicates the administrative district in which an entity was born.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
| PDg | Predicate description generation | batch_69feb3419158819082f4666077535ca9 |
completed | May 9, 2026, 4:08 a.m. |
Created at: April 27, 2026, 11:20 a.m.