Triple
T7450968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubballi-Dharwad |
E172006
|
entity |
| Predicate | roadNetworkCategory |
P74765
|
FINISHED |
| Object | major road junction in Karnataka |
—
|
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: major road junction in Karnataka | Statement: [Hubballi-Dharwad, roadNetworkCategory, major road junction in Karnataka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNetworkCategory Context triple: [Hubballi-Dharwad, roadNetworkCategory, major road junction in Karnataka]
-
A.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
B.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
C.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
D.
hasRoadNetworkType
chosen
Indicates the type or classification of road network associated with or present in an entity.
-
E.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f38c28e08190956766a5222fe720 |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.