Triple
T15626293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uri–Muzaffarabad crossing |
E375686
|
entity |
| Predicate | openedForBusService |
P119500
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Uri–Muzaffarabad crossing, openedForBusService, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForBusService Context triple: [Uri–Muzaffarabad crossing, openedForBusService, 2005]
-
A.
openedForShuttleService
Indicates that a location or facility has begun operating to provide shuttle transportation services.
-
B.
openedAsBusTunnelStation
Indicates that a station was originally opened for service as part of a bus tunnel system rather than as a conventional rail or metro station.
-
C.
openedForServiceTo
Indicates that one entity has been made available or activated to provide service or functionality to another entity.
-
D.
openedForTransilienService
Indicates that a facility or location was officially opened to provide Transilien rail service.
-
E.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9e5e248190ae54cda1fde51efb |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.