Triple
T26840929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBE |
E675772
|
entity |
| Predicate | usedInRailwayTicketsFor |
P92594
|
FINISHED |
| Object | Coimbatore Junction |
—
|
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: Coimbatore Junction | Statement: [CBE, usedInRailwayTicketsFor, Coimbatore Junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRailwayTicketsFor Context triple: [CBE, usedInRailwayTicketsFor, Coimbatore Junction]
-
A.
usedInRailwayTickets
Indicates that something is employed or applied in the context of railway tickets, such as their creation, validation, or usage.
-
B.
usedInE-tickets
Indicates that something (such as a method, technology, or feature) is employed or applied within the context of electronic tickets (e-tickets).
-
C.
usedOnRailCards
Indicates that something (such as a discount, feature, or rule) is applied to or valid for rail cards.
-
D.
usedForTicketType
chosen
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
E.
usedForRailwayTimetables
Indicates that something is employed in the creation, organization, or presentation of railway timetables.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 5:08 a.m.