Triple
T25473692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Korean railway network |
E638370
|
entity |
| Predicate | hasMajorHighSpeedServiceBrand |
P171390
|
FINISHED |
| Object | KTX |
—
|
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: KTX | Statement: [South Korean railway network, hasMajorHighSpeedServiceBrand, KTX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorHighSpeedServiceBrand Context triple: [South Korean railway network, hasMajorHighSpeedServiceBrand, KTX]
-
A.
highSpeedBrand
Indicates that a brand is associated with operating or performing at high speed compared to typical or competing brands.
-
B.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
-
C.
hasPassengerServiceBrand
chosen
Indicates that a passenger transport service operates under or is associated with a specific commercial brand or service name.
-
D.
hasLimitedExpressBrand
Indicates that an entity possesses or is associated with a Limited Express brand designation or service.
-
E.
hasHighSpeedSections
Indicates that the entity includes segments or portions where operation or movement occurs at high speed.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 21, 2026, 2:25 p.m.