Triple
T8281189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busan city buses |
E193675
|
entity |
| Predicate | usesTicketingMedium |
P9955
|
FINISHED |
| Object | RFID transport card |
—
|
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: RFID transport card | Statement: [Busan city buses, usesTicketingMedium, RFID transport card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTicketingMedium Context triple: [Busan city buses, usesTicketingMedium, RFID transport card]
-
A.
usedInE-tickets
Indicates that something (such as a method, technology, or feature) is employed or applied within the context of electronic tickets (e-tickets).
-
B.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
C.
usesFareMedium
chosen
Indicates that an entity employs a particular fare medium (such as a ticket, card, or pass) as the method of payment or validation for a trip or service.
-
D.
usesTicketValidatorType
Indicates that an entity employs or is associated with a specific type or category of ticket validation device or method.
-
E.
hasElectronicTicketing
Indicates that an entity supports or provides electronic ticketing for access, booking, or transactions.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ee66e48190af7058b14f3daac9 |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.