Triple

T15642581
Position Surface form Disambiguated ID Type / Status
Subject Jiufen E376102 entity
Predicate near P350 FINISHED
Object Keelung Mountain E77839 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: Keelung Mountain | Statement: [Jiufen, near, Keelung Mountain]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Keelung Mountain
Context triple: [Jiufen, near, Keelung Mountain]
  • A. Lyulin Mountain
    Lyulin Mountain is a small mountain range in western Bulgaria, located just southwest of Sofia and known for its forested hills and hiking trails.
  • B. Yangmingshan chosen
    Yangmingshan is a volcanic national park area near Taipei in northern Taiwan, known for its hot springs, hiking trails, and scenic mountain landscapes.
  • C. Songshan
    Songshan is one of China's Five Great Mountains, renowned as a sacred Taoist and Buddhist site and home to the historic Shaolin Monastery.
  • D. Alishan
    Alishan is a renowned mountainous scenic area in Taiwan famous for its forest railway, sea of clouds, sunrises, and ancient cypress forests.
  • E. Fongshan
    Fongshan is a district in Kaohsiung, Taiwan, known for its historical military sites and role as a former administrative center.
  • 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_69d85cd035a48190b73d5579ab73969a completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ed23d688190bea996f90989d406 completed April 16, 2026, 2:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff5f4d49188190855a895c5844dee0 completed May 9, 2026, 4:22 p.m.
Created at: April 10, 2026, 4:15 a.m.