Triple
T2286522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmwood neighborhood of Berkeley |
E51402
|
entity |
| Predicate | hasStreetTreeCharacter |
P20885
|
FINISHED |
| Object | tree-lined residential streets |
—
|
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: tree-lined residential streets | Statement: [Elmwood neighborhood of Berkeley, hasStreetTreeCharacter, tree-lined residential streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetTreeCharacter Context triple: [Elmwood neighborhood of Berkeley, hasStreetTreeCharacter, tree-lined residential streets]
-
A.
hasTreeLinedStreets
chosen
Indicates that the streets in a given area are lined or bordered with trees along their sides.
-
B.
hasTrees
Indicates that something possesses or contains one or more trees.
-
C.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
D.
hasTreeVigor
Indicates the assessed strength, health, and growth potential of a tree in relation to its current condition or environment.
-
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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc24730208190af8a5cf443d334f7 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.