Triple
T3137876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundelkhand Expressway |
E65576
|
entity |
| Predicate | futureExpansion |
P14356
|
FINISHED |
| Object | 6 lanes |
—
|
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: 6 lanes | Statement: [Bundelkhand Expressway, futureExpansion, 6 lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureExpansion Context triple: [Bundelkhand Expressway, futureExpansion, 6 lanes]
-
A.
futureEvolution
Indicates a predicted or potential future development or transformation of one entity into another.
-
B.
expands
chosen
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
C.
futureSiteOf
Indicates that a location is planned or designated to become the site of a particular entity or structure in the future.
-
D.
majorExpansionUnder
Indicates that one entity is undergoing or has undergone a significant enlargement, growth, or extension while being under the authority, control, or scope of another entity.
-
E.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada574509c81908a88bb10ea35516d |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.