Triple

T15494338
Position Surface form Disambiguated ID Type / Status
Subject Anyang Museum E378774 entity
Predicate mainTerritoryOfActivity P19850 FINISHED
Object Anyang E77170 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: Anyang | Statement: [Anyang Museum, mainTerritoryOfActivity, Anyang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anyang
Context triple: [Anyang Museum, mainTerritoryOfActivity, Anyang]
  • A. Anyang chosen
    Anyang is an ancient city in northern China renowned as one of the historical capitals of the Shang dynasty and a major archaeological site.
  • B. Anyang
    Anyang is a mid-sized South Korean city in the Seoul Capital Area known for its residential districts, light industry, and proximity to central Seoul.
  • C. Sanhe City
    Sanhe City is a county-level city in Hebei Province, China, located near Beijing and forming part of the Beijing–Tianjin–Hebei metropolitan region.
  • D. Taian
    Taian is a prefecture-level city in eastern China's Shandong province, best known as the gateway to the sacred Mount Tai.
  • E. Hejin
    Hejin is a county-level city in southern Shanxi Province, China, situated along the Fen River near its confluence with the Yellow River.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03fad723481908d2aa33e8f065f2f completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff4c345f888190be7a684f3bd86324 completed May 9, 2026, 3:01 p.m.
Created at: April 10, 2026, 3:49 a.m.