Triple
T29152188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badami railway station |
E738938
|
entity |
| Predicate | hasFootOverbridge |
P25561
|
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: [Badami railway station, hasFootOverbridge, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootOverbridge Context triple: [Badami railway station, hasFootOverbridge, yes]
-
A.
hasFootbridge
chosen
Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
-
B.
hasFootbridgeOrigin
Indicates that a footbridge originates, starts, or has its starting point at the referenced location or entity.
-
C.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
-
D.
hasBridgeUnderpasses
Indicates that one structure, typically a bridge, includes or provides underpasses that allow passage beneath it.
-
E.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 28, 2026, 11:42 a.m.