Triple
T26840930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBE |
E675772
|
entity |
| Predicate | usedInOnlineBookingFor |
P39114
|
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, usedInOnlineBookingFor, Coimbatore Junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInOnlineBookingFor Context triple: [CBE, usedInOnlineBookingFor, Coimbatore Junction]
-
A.
hasOnlineReservation
Indicates that an entity has a booking or reservation that was made or is managed through an online system.
-
B.
usesBookingCode
Indicates that one entity makes use of a specific booking code associated with another entity or transaction.
-
C.
alsoBookableAs
Indicates that one entity can be reserved or booked in an alternative way or under an alternative option represented by another entity.
-
D.
allowsReservationsOn
chosen
Indicates that one entity permits making reservations or bookings for another entity.
-
E.
indicatedInHotelsBy
Indicates that something is highlighted, referenced, or made known within hotels by a particular source or agent.
- 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_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 5:08 a.m.