Triple
T30133149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honam High-Speed Railway |
E765902
|
entity |
| Predicate | primaryTerminusRegionSouth |
P51586
|
FINISHED |
| Object | Honam region |
E168598
|
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: Honam region | Statement: [Honam High-Speed Railway, primaryTerminusRegionSouth, Honam region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTerminusRegionSouth Context triple: [Honam High-Speed Railway, primaryTerminusRegionSouth, Honam region]
-
A.
southTerminusRegion
chosen
Indicates that a given region serves as the southern endpoint or terminus of a specified route, feature, or entity.
-
B.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
-
C.
southTerminusType
Indicates the type or nature of the southern endpoint or terminus of something (such as a route, line, or boundary).
-
D.
easternTerminusRegion
Indicates the region in which something (such as a route, line, or path) has its eastern endpoint or terminus.
-
E.
regionTypeSouth
Indicates that one region is classified as being in the southern part or of a southern type relative to a larger geographic or conceptual area.
- F. None of above.
Provenance (4 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f46ab264c8190971e9be54df04f95 |
completed | June 15, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
Created at: April 29, 2026, 7:15 p.m.