Triple
T5787515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunset Hill neighborhood |
E128303
|
entity |
| Predicate | streetscape |
P45553
|
FINISHED |
| Object | landscaped lawns |
—
|
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: landscaped lawns | Statement: [Sunset Hill neighborhood, streetscape, landscaped lawns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetscape Context triple: [Sunset Hill neighborhood, streetscape, landscaped lawns]
-
A.
isPartOfStreetscape
chosen
Indicates that something forms a component or element within the overall layout or visual composition of a streetscape.
-
B.
cityScene
Indicates a scene or setting that takes place within an urban or city environment.
-
C.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
-
D.
cityPanorama
Indicates a wide, comprehensive visual view or representation of a cityscape, typically encompassing many of its features in a single scene.
-
E.
hasStreetEnvironment
Indicates that an entity is associated with or characterized by a particular type or quality of street-level surroundings or conditions.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a5297c88190bd28adb2552a26f4 |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.