Triple
T16697326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assandh |
E405747
|
entity |
| Predicate | hasNearbyRailConnectivity |
P31869
|
FINISHED |
| Object | stations on major routes in Karnal district |
—
|
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: stations on major routes in Karnal district | Statement: [Assandh, hasNearbyRailConnectivity, stations on major routes in Karnal district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyRailConnectivity Context triple: [Assandh, hasNearbyRailConnectivity, stations on major routes in Karnal district]
-
A.
hasNearbyRailway
Indicates that one entity is located close to a railway associated with or relevant to another entity.
-
B.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
C.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
D.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
E.
hasNearbyRailwayStation
chosen
Indicates that a railway station is located within a short or convenient distance from the referenced entity.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3832e93c48190a594c498e9cc901a |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.