Triple
T8281190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busan city buses |
E193675
|
entity |
| Predicate | usesTicketingMedium |
P9955
|
FINISHED |
| Object | mobile transport card app (via Korean payment apps) |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: mobile transport card app (via Korean payment apps) | Statement: [Busan city buses, usesTicketingMedium, mobile transport card app (via Korean payment apps)]
Provenance (2 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_69cbd11ed22c819082bf036602eaa038 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 5:51 p.m.