Triple

T7251594
Position Surface form Disambiguated ID Type / Status
Subject Centum City E157613 entity
Predicate servedBy P82 FINISHED
Object Busan Metro Line 2 E689798 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: Busan Metro Line 2 | Statement: [Centum City, servedBy, Busan Metro Line 2]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Busan Metro Line 2
Context triple: [Centum City, servedBy, Busan Metro Line 2]
  • A. Busan Metro Line 2 chosen
    Busan Metro Line 2 is a major east–west subway line in Busan, South Korea, connecting key residential, commercial, and industrial areas across the city.
  • B. Daegu Metro Line 2
    Daegu Metro Line 2 is an east–west rapid transit line in Daegu, South Korea, forming a key part of the city's urban rail network.
  • C. Busan Metro
    Busan Metro is the rapid transit system serving the city of Busan, South Korea, providing extensive urban and suburban rail transportation across the metropolitan area.
  • D. Daegu Metro Line 3
    Daegu Metro Line 3 is a monorail rapid transit line in Daegu, South Korea, forming part of the city's urban rail network.
  • E. Daegu Metro Line 1
    Daegu Metro Line 1 is a major rapid transit line in Daegu, South Korea, notable as the line on which the deadly 2003 Daegu subway fire occurred.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c6882d81d4819085f7ff862951ee4f completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ea7ae0e48190bd80c91bad1976c6 completed March 27, 2026, 8:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69c9162980708190be2a347b2322c09c completed March 29, 2026, 12:08 p.m.
Created at: March 27, 2026, 2:56 p.m.