Triple
T37516917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIVB |
E932657
|
entity |
| Predicate | usesTicketBrand |
P136845
|
FINISHED |
| Object | Brupass |
—
|
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: Brupass | Statement: [MIVB, usesTicketBrand, Brupass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTicketBrand Context triple: [MIVB, usesTicketBrand, Brupass]
-
A.
usedByTicket
Indicates that something (such as a resource, item, or service) is utilized or referenced by a specific ticket.
-
B.
ticketingBrandAccepted
chosen
Indicates that a particular ticketing brand is recognized and accepted for use in a given context or system.
-
C.
usesTicketZone
Indicates that an entity’s validity, access, or operation is determined by or restricted to a specific ticket zone.
-
D.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
E.
ticketBranding
Indicates that one entity defines or is associated with the branding or visual identity applied to a ticket-related entity.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:17 p.m.