Triple
T34991936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queenstown Road |
E1009410
|
entity |
| Predicate | isThoroughfareFor |
P182184
|
FINISHED |
| Object | localTrafficInBattersea |
—
|
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: localTrafficInBattersea | Statement: [Queenstown Road, isThoroughfareFor, localTrafficInBattersea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isThoroughfareFor Context triple: [Queenstown Road, isThoroughfareFor, localTrafficInBattersea]
-
A.
isKeyThoroughfareIn
Indicates that a thoroughfare (such as a road or route) serves as a primary or major access way within a specified area or region.
-
B.
isSideStreetOf
Indicates that one street is a smaller, less prominent road that connects to or branches off from another main street.
-
C.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
D.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
E.
isMajorCommercialStreetOf
Indicates that a street serves as a primary, heavily used route for commercial activity within a specified area or locality.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.