Triple
T27383425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germantown Avenue |
E691296
|
entity |
| Predicate | roadSurfaceIncludes |
P78490
|
FINISHED |
| Object | cobblestone or Belgian block |
—
|
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: cobblestone or Belgian block | Statement: [Germantown Avenue, roadSurfaceIncludes, cobblestone or Belgian block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadSurfaceIncludes Context triple: [Germantown Avenue, roadSurfaceIncludes, cobblestone or Belgian block]
-
A.
laneSurface
Indicates the type or condition of the surface that makes up a lane used for travel or traffic.
-
B.
roadEnvironment
Indicates that the relationship or action occurs within, is influenced by, or is specifically associated with a road or roadway environment.
-
C.
hasRoadCondition
chosen
Indicates that a specified road segment possesses or is characterized by a particular condition or state (e.g., quality, surface, or status).
-
D.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
-
E.
roadSide
Indicates that one entity is located along, beside, or immediately adjacent to a road.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:23 p.m.