Triple
T13949075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midwood |
E335469
|
entity |
| Predicate | hasStreetCharacteristic |
P105429
|
FINISHED |
| Object | tree-lined |
—
|
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 | Statement: [Midwood, hasStreetCharacteristic, tree-lined]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetCharacteristic Context triple: [Midwood, hasStreetCharacteristic, tree-lined]
-
A.
hasRoadCharacteristics
chosen
Indicates that one entity possesses specific road-related features or attributes, such as type, condition, or structural properties.
-
B.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
C.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
D.
hasNotableStreet
Indicates that an entity is associated with a particular street that is considered notable or significant.
-
E.
hasSideStreetType
Indicates that an entity (such as a street or road segment) is associated with a specific type or classification of side street.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e12171c8190b95746bdd4845def |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.