Triple
T36264156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clock Tower, Leicester |
E892175
|
entity |
| Predicate | streetConvergence |
P182872
|
FINISHED |
| Object | Gallowtree Gate |
—
|
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: Gallowtree Gate | Statement: [Clock Tower, Leicester, streetConvergence, Gallowtree Gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetConvergence Context triple: [Clock Tower, Leicester, streetConvergence, Gallowtree Gate]
-
A.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
-
B.
numberOfConvergingStreets
Indicates the count of distinct streets that meet or intersect at a particular junction or location.
-
C.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
D.
convergesRoad
chosen
Indicates that one road comes together with or joins another road at a common point or segment.
-
E.
streetPatternFocusedOn
Indicates a relationship where a street pattern is organized, oriented, or designed with primary emphasis on a particular feature, area, or organizing element.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b624a9988190871ef23197ec13b2 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.