Triple
T29152198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badami railway station |
E738938
|
entity |
| Predicate | servesHistoricTown |
P195130
|
FINISHED |
| Object | Badami |
—
|
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: Badami | Statement: [Badami railway station, servesHistoricTown, Badami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesHistoricTown Context triple: [Badami railway station, servesHistoricTown, Badami]
-
A.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
B.
governsHistoricTown
Indicates that one entity exercises official governing authority over a town that is recognized as historically significant.
-
C.
historicalMainTown
Indicates that one place served as the primary or principal town for another place during a specific historical period.
-
D.
hasHistoricTownRights
Indicates that an entity possesses officially granted historic town rights, typically conferring a traditional legal or municipal status as a town.
-
E.
hasHistoricTownSquare
Indicates that an entity possesses or includes a town square that is of historical significance.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
| PDg | Predicate description generation | batch_69fda945e1e08190bf923fcd4d2c548a |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 28, 2026, 11:43 a.m.