Triple

T7376801
Position Surface form Disambiguated ID Type / Status
Subject University of Ulsan E170145 entity
Predicate city P40 FINISHED
Object Ulsan E28895 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: Ulsan | Statement: [University of Ulsan, city, Ulsan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulsan
Context triple: [University of Ulsan, city, Ulsan]
  • A. Ulsan chosen
    Ulsan is a major industrial city in southeastern South Korea, known for its large automobile, shipbuilding, and petrochemical complexes.
  • B. Changwon
    Changwon is a major industrial and administrative city in South Gyeongsang Province, South Korea, known for its planned urban layout and role as a regional government and manufacturing hub.
  • C. Gijeon
    Gijeon is an alternative name for the Seoul Capital Area, the densely populated metropolitan region surrounding South Korea’s capital city.
  • D. Pohang
    Pohang is a major industrial and port city in South Korea, best known as the home of the global steelmaker POSCO and a key hub on the country’s east coast.
  • E. Daegu
    Daegu is a major metropolitan city in southeastern South Korea known for its textile industry, electronics manufacturing, and cultural festivals.
  • 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_69c68a5bfaac81909ce7f001dfb70c76 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f1a8b18c8190ad1a19521eda2319 completed March 27, 2026, 9:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69e6e6968aec8190a9d1e51ac7e87853 completed April 21, 2026, 2:53 a.m.
Created at: March 27, 2026, 3:07 p.m.