Triple
T35447616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GZB |
E1024528
|
entity |
| Predicate | usedInTicketingSystemOf |
P25925
|
FINISHED |
| Object | Indian Railways |
—
|
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: Indian Railways | Statement: [GZB, usedInTicketingSystemOf, Indian Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTicketingSystemOf Context triple: [GZB, usedInTicketingSystemOf, Indian Railways]
-
A.
primaryTicketingSystem
Indicates that one ticketing system is designated as the main or default system used for handling tickets in a given context.
-
B.
ticketSystem
chosen
Indicates a relationship where an entity is managed, tracked, or processed through a ticket-based system for handling requests, issues, or tasks.
-
C.
ticketSystemType
Indicates the type or category of ticketing system associated with an entity or interaction.
-
D.
ticketingSystemOperator
Indicates that one entity operates, manages, or administers the ticketing system used for issuing, tracking, or processing tickets for another entity or context.
-
E.
usedByTicket
Indicates that something (such as a resource, item, or service) is utilized or referenced by a specific ticket.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:04 p.m.