Triple
T27741918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line (Delhi Metro) |
E701875
|
entity |
| Predicate | extensionOpenedTo |
P165097
|
FINISHED |
| Object | Bahadurgarh |
—
|
NE NERFINISHED |
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: Bahadurgarh | Statement: [Green Line (Delhi Metro), extensionOpenedTo, Bahadurgarh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensionOpenedTo Context triple: [Green Line (Delhi Metro), extensionOpenedTo, Bahadurgarh]
-
A.
extensionOpenedIn
Indicates that a particular extension is opened or activated within a specified application, environment, or context.
-
B.
extensionOpened
Indicates that a software extension has been activated or launched from its previously closed or inactive state.
-
C.
extensionOpenedWith
Indicates that a file extension is opened or handled using a particular application or tool.
-
D.
extensionOpening
Indicates that one entity serves as an opening or access point that leads into or connects to an extension of another entity.
-
E.
extensionOpenedToMernda
Indicates that a transport or infrastructure extension has been opened or extended to reach Mernda.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 4:12 p.m.