Triple
T5980114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyongyang Metro |
E133097
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object |
Samhung Station
Samhung Station is a stop on the Pyongyang Metro system in North Korea’s capital city.
|
E570243
|
NE FINISHED |
How this triple was built (4 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: Samhung Station | Statement: [Pyongyang Metro, hasStation, Samhung Station]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Samhung Station Context triple: [Pyongyang Metro, hasStation, Samhung Station]
-
A.
Kwangbok Station
Kwangbok Station is a stop on the Pyongyang Metro system in North Korea, serving passengers along one of the capital’s main underground transit lines.
-
B.
Jagalchi Station
Jagalchi Station is a subway station in Busan, South Korea, serving the bustling Jagalchi Fish Market area and nearby downtown attractions.
-
C.
Beomeosa Station
Beomeosa Station is a subway station in Busan, South Korea, serving as a key access point to the nearby Beomeosa Temple and surrounding Geumjeong District area.
-
D.
Yeonsan Station
Yeonsan Station is a major transit hub in Busan, South Korea, serving as an important interchange point on the city’s subway network.
-
E.
Myeongnyun Station
Myeongnyun Station is a metro station in Busan, South Korea, serving the Dongnae District on the Busan Metro network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Samhung Station Triple: [Pyongyang Metro, hasStation, Samhung Station]
Generated description
Samhung Station is a stop on the Pyongyang Metro system in North Korea’s capital city.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Samhung Station Target entity description: Samhung Station is a stop on the Pyongyang Metro system in North Korea’s capital city.
-
A.
Kwangbok Station
Kwangbok Station is a stop on the Pyongyang Metro system in North Korea, serving passengers along one of the capital’s main underground transit lines.
-
B.
Jagalchi Station
Jagalchi Station is a subway station in Busan, South Korea, serving the bustling Jagalchi Fish Market area and nearby downtown attractions.
-
C.
Beomeosa Station
Beomeosa Station is a subway station in Busan, South Korea, serving as a key access point to the nearby Beomeosa Temple and surrounding Geumjeong District area.
-
D.
Yeonsan Station
Yeonsan Station is a major transit hub in Busan, South Korea, serving as an important interchange point on the city’s subway network.
-
E.
Myeongnyun Station
Myeongnyun Station is a metro station in Busan, South Korea, serving the Dongnae District on the Busan Metro network.
- 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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a40233081909c04f62ec0382bfd |
completed | March 22, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1355db96c8190b40b32b8d3a5dbdf |
completed | March 23, 2026, 12:43 p.m. |
| NEDg | Description generation | batch_69c13784569c819084aea01ac3d2c5dc |
completed | March 23, 2026, 12:52 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c137fd85cc8190ad213d3462e39d5c |
completed | March 23, 2026, 12:54 p.m. |
Created at: March 22, 2026, 4:04 p.m.