Triple
T19897109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltal–Domel track |
E478178
|
entity |
| Predicate | languageUsedAlongRoute |
P87746
|
FINISHED |
| Object | Kashmiri |
—
|
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: Kashmiri | Statement: [Baltal–Domel track, languageUsedAlongRoute, Kashmiri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedAlongRoute Context triple: [Baltal–Domel track, languageUsedAlongRoute, Kashmiri]
-
A.
languageUsedOnRoute
chosen
Indicates that a particular language is used for communication (e.g., signage, announcements, or information) along a specific route.
-
B.
languageRegionsAlongRoute
Indicates the languages spoken in the geographic regions that lie along a specified route.
-
C.
languageOfRouteCountries
Indicates the languages used or officially spoken in the countries through which a given route passes.
-
D.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
E.
includesLanguagesSpokenAlong
Indicates that something (such as a region, route, or area) encompasses or contains the set of languages spoken along its extent or within its boundaries.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6593dba78819082c8b80e65246171 |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.