Triple
T30513125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongbu Line (local services) |
E776483
|
entity |
| Predicate | primaryRouteStart |
P203903
|
FINISHED |
| Object | Seoul Station |
E467238
|
NE 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 Station | Statement: [Gyeongbu Line (local services), primaryRouteStart, Seoul Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRouteStart Context triple: [Gyeongbu Line (local services), primaryRouteStart, Seoul Station]
-
A.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
B.
primaryRouteFrom
Indicates that one entity serves as the main or preferred route originating from another entity.
-
C.
primaryRouteOf
Indicates that one route is the main or most important pathway used for reaching or connecting to a particular destination or entity.
-
D.
primaryRoutes
Indicates the main or most important routes that connect or serve between specified locations or entities.
-
E.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
- F. None of above. chosen
Provenance (5 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_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41c2613e5481908c6add7a3b1ca22e |
completed | June 29, 2026, 12:54 a.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_6a024936acc48190bc4a9abe4c519302 |
completed | May 11, 2026, 9:25 p.m. |
Created at: April 29, 2026, 8:16 p.m.