Triple
T35626479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent Street Quadrant reconstruction (London) |
E1029469
|
entity |
| Predicate | streetSection |
P5397
|
FINISHED |
| Object | Regent Street Quadrant |
—
|
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: Regent Street Quadrant | Statement: [Regent Street Quadrant reconstruction (London), streetSection, Regent Street Quadrant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetSection Context triple: [Regent Street Quadrant reconstruction (London), streetSection, Regent Street Quadrant]
-
A.
streetSectionOf
chosen
Indicates that one street segment or portion belongs to, is contained within, or forms part of a larger street or roadway.
-
B.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
C.
streetOrArea
Indicates that one entity is a street or area associated with, located at, or relevant to the other entity.
-
D.
streetOrientedAlong
Indicates that a street is aligned or runs in the same general direction as a specified reference feature or axis.
-
E.
urbanSegmentName
Indicates the specific name assigned to a segment within an urban area or city layout.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.