Triple
T28641654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulsan–Pohang section |
E724939
|
entity |
| Predicate | railwayLineName |
P28725
|
FINISHED |
| Object | Ulsan–Pohang section of the Donghae Line |
—
|
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: Ulsan–Pohang section of the Donghae Line | Statement: [Ulsan–Pohang section, railwayLineName, Ulsan–Pohang section of the Donghae Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineName Context triple: [Ulsan–Pohang section, railwayLineName, Ulsan–Pohang section of the Donghae Line]
-
A.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
railwayName
Indicates the name assigned to a specific railway or railway line in the relationship.
-
C.
lineName
chosen
Indicates the specific name or designation assigned to a particular line (such as a route, path, or service) that distinguishes it from other lines.
-
D.
railwayLineNumber
Indicates the identifying number assigned to a specific railway line within a rail network.
-
E.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 4:45 a.m.