Triple
T14233236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kilburn, London, England |
E352807
|
entity |
| Predicate | highStreetRunsAlong |
P76449
|
FINISHED |
| Object | A5 road |
E295818
|
NE 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: A5 road | Statement: [Kilburn, London, England, highStreetRunsAlong, A5 road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highStreetRunsAlong Context triple: [Kilburn, London, England, highStreetRunsAlong, A5 road]
-
A.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
B.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
C.
streetOrientedAlong
chosen
Indicates that a street is aligned or runs in the same general direction as a specified reference feature or axis.
-
D.
hasStreetRunningTracks
Indicates that a location or area includes street-level tracks used for running or jogging.
-
E.
hasParallelStreet
Indicates that one street runs parallel to another street, maintaining a constant distance without intersecting.
- F. None of above.
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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622cdd6481908befa179a9675bb5 |
completed | April 14, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0facddecc08190b8054df90457baf3 |
completed | May 22, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.