Triple

T31998758
Position Surface form Disambiguated ID Type / Status
Subject Gyeongwon Line E817062 entity
Predicate gainedCurrentRole P154730 FINISHED
Object after creation of Seoul Metropolitan Subway Line 1 LITERAL 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: after creation of Seoul Metropolitan Subway Line 1 | Statement: [Gyeongwon Line, gainedCurrentRole, after creation of Seoul Metropolitan Subway Line 1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: gainedCurrentRole
Context triple: [Gyeongwon Line, gainedCurrentRole, after creation of Seoul Metropolitan Subway Line 1]
  • A. eraOfCurrentRole
    Indicates the historical or temporal era during which the entity’s current role or position is held.
  • B. gainedStatus chosen
    Indicates that an entity has acquired or achieved a particular status, condition, or role as a result of some event or process.
  • C. returnedToRole
    Indicates that an entity resumed or went back to a role or position it previously held.
  • D. subsequentRole
    Indicates that one role or position is held after, and in succession to, another role or position.
  • E. roleAfterConversion
    Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
  • F. None of above.

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_69f348f8ce388190ae84376b1f348f12 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6cd126fcc8190aa1f1f146e45ec0c completed May 3, 2026, 4:20 a.m.
PD Predicate disambiguation batch_69f6cc1470808190b70cdfd7a6395670 completed May 3, 2026, 4:16 a.m.
Created at: May 1, 2026, 12:14 a.m.