Triple
T13592201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi–Mumbai Expressway |
E324718
|
entity |
| Predicate | hasUnderpasses |
P24311
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Delhi–Mumbai Expressway, hasUnderpasses, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderpasses Context triple: [Delhi–Mumbai Expressway, hasUnderpasses, yes]
-
A.
hasUnderpass
chosen
Indicates that one location or structure includes or is connected by an underpass beneath another feature or pathway.
-
B.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
-
C.
hasBridgeUnderpasses
Indicates that one structure, typically a bridge, includes or provides underpasses that allow passage beneath it.
-
D.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
E.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb056ce088190a6feb4266633d18b |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.