Triple
T1710908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busan Metro |
E36979
|
entity |
| Predicate | hasDepot |
P2413
|
FINISHED |
| Object |
Daejeo Depot
Daejeo Depot is a maintenance and storage facility serving the Busan Metro system in Busan, South Korea.
|
E197856
|
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: Daejeo Depot | Statement: [Busan Metro, hasDepot, Daejeo Depot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Daejeo Depot Context triple: [Busan Metro, hasDepot, Daejeo Depot]
-
A.
Jangsan Depot
Jangsan Depot is a maintenance and storage facility serving trains on the Busan Metro system in Busan, South Korea.
-
B.
Daejeon Station
Daejeon Station is a major railway hub in central South Korea, serving high-speed KTX trains and connecting Daejeon to key cities nationwide.
-
C.
Nampo Station
Nampo Station is a major subway station and commercial hub in central Busan, South Korea, known for its proximity to popular shopping streets and tourist attractions.
-
D.
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.
-
E.
Sasang Station
Sasang Station is a major railway and subway interchange in Busan, South Korea, serving as a key transit hub for both local and intercity travel.
- 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: Daejeo Depot Triple: [Busan Metro, hasDepot, Daejeo Depot]
Generated description
Daejeo Depot is a maintenance and storage facility serving the Busan Metro system in Busan, South Korea.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Daejeo Depot Target entity description: Daejeo Depot is a maintenance and storage facility serving the Busan Metro system in Busan, South Korea.
-
A.
Jangsan Depot
Jangsan Depot is a maintenance and storage facility serving trains on the Busan Metro system in Busan, South Korea.
-
B.
Daejeon Station
Daejeon Station is a major railway hub in central South Korea, serving high-speed KTX trains and connecting Daejeon to key cities nationwide.
-
C.
Nampo Station
Nampo Station is a major subway station and commercial hub in central Busan, South Korea, known for its proximity to popular shopping streets and tourist attractions.
-
D.
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.
-
E.
Sasang Station
Sasang Station is a major railway and subway interchange in Busan, South Korea, serving as a key transit hub for both local and intercity travel.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa63149288819082e7055d0d292d1d |
completed | March 6, 2026, 5:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ada97dfb1c819084e750a8550d3e82 |
completed | March 8, 2026, 4:53 p.m. |
| NEDg | Description generation | batch_69adab0295b8819092cb51082337b97b |
completed | March 8, 2026, 4:59 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69adaea486d0819097357d881b70d114 |
completed | March 8, 2026, 5:15 p.m. |
Created at: March 4, 2026, 7:30 p.m.