Triple
T28193754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul–Busan |
E716382
|
entity |
| Predicate | servedByExpressBusService |
P39381
|
FINISHED |
| Object | Seoul–Busan express buses |
—
|
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: Seoul–Busan express buses | Statement: [Seoul–Busan, servedByExpressBusService, Seoul–Busan express buses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByExpressBusService Context triple: [Seoul–Busan, servedByExpressBusService, Seoul–Busan express buses]
-
A.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
B.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
C.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
D.
connectsToBusAt
Indicates that one entity has an access or transfer point where it links to a bus service at a specific location or stop.
-
E.
hasNightBusService
Indicates that a transportation route or stop is served by buses operating during nighttime hours.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 27, 2026, 10:26 p.m.