Triple
T17434593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koregaon Park |
E423967
|
entity |
| Predicate | hasRoadPattern |
P105429
|
FINISHED |
| Object | tree-lined avenues |
—
|
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 avenues | Statement: [Koregaon Park, hasRoadPattern, tree-lined avenues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadPattern Context triple: [Koregaon Park, hasRoadPattern, tree-lined avenues]
-
A.
hasPavementPattern
Indicates that an entity possesses or is characterized by a specific pattern or design in its pavement surface.
-
B.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
C.
hasRoadConfiguration
Indicates that there exists a specific arrangement or layout of roads associated with or characterizing an entity.
-
D.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
E.
hasRoadCharacteristics
chosen
Indicates that one entity possesses specific road-related features or attributes, such as type, condition, or structural properties.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4490361c081908fd24f9a812f212c |
completed | April 19, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.