Triple
T12622061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa Street and Sierra Madre Boulevard, Pasadena |
E301404
|
entity |
| Predicate | roadType2 |
P1019
|
FINISHED |
| Object | boulevard |
—
|
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: boulevard | Statement: [Villa Street and Sierra Madre Boulevard, Pasadena, roadType2, boulevard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadType2 Context triple: [Villa Street and Sierra Madre Boulevard, Pasadena, roadType2, boulevard]
-
A.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
C.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
D.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
E.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:14 p.m.