Triple
T31095167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernakulam Junction railway station |
E792503
|
entity |
| Predicate | hasTrainFrequency |
P20359
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Ernakulam Junction railway station, hasTrainFrequency, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainFrequency Context triple: [Ernakulam Junction railway station, hasTrainFrequency, high]
-
A.
transitFrequencyApprox
chosen
Indicates an approximate rate or regularity with which a transit event or service occurs between entities.
-
B.
hasRegionalTrainService
Indicates that a location or route is served by regional train services connecting it to nearby areas.
-
C.
hasNightTrainService
Indicates that a transportation route or station is served by trains that operate during nighttime hours.
-
D.
servedByTrainAtAllTimes
Indicates that a location or route is continuously provided with train service at all times within the relevant operating period.
-
E.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: April 29, 2026, 9:03 p.m.