Triple
T30133148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honam High-Speed Railway |
E765902
|
entity |
| Predicate | primaryTerminusRegionNorth |
P51970
|
FINISHED |
| Object | Seoul area |
E166134
|
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 area | Statement: [Honam High-Speed Railway, primaryTerminusRegionNorth, Seoul area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTerminusRegionNorth Context triple: [Honam High-Speed Railway, primaryTerminusRegionNorth, Seoul area]
-
A.
northernTerminusRegion
chosen
Indicates that a location or route has its northern endpoint or final stopping point within a specified region.
-
B.
northTerminusRegion
Indicates that a specified region serves as the northern endpoint or terminus of a linear feature, route, or entity.
-
C.
easternTerminusRegion
Indicates the region in which something (such as a route, line, or path) has its eastern endpoint or terminus.
-
D.
northernTerminusVariant
Indicates that one location or feature serves as an alternative or variant northern endpoint of a route, line, or path.
-
E.
regionTypeNorth
Indicates that one region is classified as the northern part or northern type relative to another region or a larger geographic context.
- 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_6a01c74a72fc819084826c6c292af03a |
completed | May 11, 2026, 12:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a293885231c81909ccb06d9b7ca0936 |
completed | June 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a01c624103c819087cb35a71c5868b6 |
completed | May 11, 2026, 12:05 p.m. |
Created at: April 29, 2026, 7:15 p.m.