Triple
T19279443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phagwara |
E482147
|
entity |
| Predicate | stateHighwayConnectivity |
P135422
|
FINISHED |
| Object | well connected by road |
—
|
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: well connected by road | Statement: [Phagwara, stateHighwayConnectivity, well connected by road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHighwayConnectivity Context triple: [Phagwara, stateHighwayConnectivity, well connected by road]
-
A.
nationalHighwayConnectivity
Indicates the extent to which locations are linked by a network of national highways enabling direct or efficient road travel between them.
-
B.
nationalHighwayNetworkState
Indicates that a state is part of, or associated with, the national highway network.
-
C.
stateHighwayServedBy
Indicates that a particular state highway is provided service or coverage by a specified transportation route, agency, or facility.
-
D.
stateRouteConnection
Indicates a relationship where a state-level route connects or links two locations or transportation segments.
-
E.
stateHighwayDesignationIn
Indicates that a roadway has been designated as a state highway within a specified jurisdiction or region.
- F. None of above. chosen
Provenance (4 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbf817c819098745ed365cda4a9 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:30 p.m.