Triple
T29043407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulsan urban bus network |
E738060
|
entity |
| Predicate | transportationModeIn |
P114694
|
FINISHED |
| Object | Ulsan industrial zones |
—
|
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: Ulsan industrial zones | Statement: [Ulsan urban bus network, transportationModeIn, Ulsan industrial zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationModeIn Context triple: [Ulsan urban bus network, transportationModeIn, Ulsan industrial zones]
-
A.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
B.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
C.
isPublicTransportIn
chosen
Indicates that a mode or instance of public transportation operates within, serves, or is located in a specified area or region.
-
D.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
E.
usesTransportNetwork
Indicates that an entity makes use of a transport network (such as roads, rail, or transit systems) to move people, goods, or services.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 28, 2026, 10:03 a.m.