Triple
T10790897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chittenango, New York |
E254573
|
entity |
| Predicate | roadSurfaceTheme |
P41604
|
FINISHED |
| Object | yellow brick motif in downtown |
—
|
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: yellow brick motif in downtown | Statement: [Chittenango, New York, roadSurfaceTheme, yellow brick motif in downtown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadSurfaceTheme Context triple: [Chittenango, New York, roadSurfaceTheme, yellow brick motif in downtown]
-
A.
roadEnvironment
Indicates that the relationship or action occurs within, is influenced by, or is specifically associated with a road or roadway environment.
-
B.
hasRoadCondition
Indicates that a specified road segment possesses or is characterized by a particular condition or state (e.g., quality, surface, or status).
-
C.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
-
D.
roadSide
Indicates that one entity is located along, beside, or immediately adjacent to a road.
-
E.
streetMaterial
chosen
Indicates the material composition from which a street or road surface is made.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f5b8248190a633dc44ae620a3a |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.