Triple
T30513145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongbu Line (local services) |
E776483
|
entity |
| Predicate | higherSpeedServiceOnSameCorridor |
P145129
|
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: [Gyeongbu Line (local services), higherSpeedServiceOnSameCorridor, KTX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherSpeedServiceOnSameCorridor Context triple: [Gyeongbu Line (local services), higherSpeedServiceOnSameCorridor, KTX]
-
A.
hasHighSpeedElevators
Indicates that a building or structure is equipped with elevators capable of operating at high speeds.
-
B.
hasServiceOnCorridor
Indicates that a service operates along, or is provided on, a specific corridor or route.
-
C.
rushHourServicePattern
Indicates that a service operates according to a specific pattern or schedule that applies only during rush-hour or peak travel times.
-
D.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
-
E.
hasHighSpeedSections
chosen
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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 8:16 p.m.