Triple

T21623135
Position Surface form Disambiguated ID Type / Status
Subject Naksan E533626 entity
Predicate romanization P2508 FINISHED
Object Naksan NE NERFINISHED

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: Naksan | Statement: [Naksan, romanization, Naksan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Naksan
Context triple: [Naksan, romanization, Naksan]
  • A. Naksan chosen
    Naksan is a small but prominent mountain in central Seoul, South Korea, known for its city views, walking trails, and sections of the restored Seoul City Wall.
  • B. Ninalla
    Ninalla was the wife of Gudea, the prominent ruler (ensi) of the Sumerian city-state of Lagash in the late 3rd millennium BCE.
  • C. Neseenan
    Neseenan is an alternative name for the Nisenan language, an indigenous language of the Nisenan people of Northern California.
  • D. Nivala
    Nivala is a small town and municipality in Northern Ostrobothnia, Finland, known for its rural character and agricultural surroundings.
  • E. Naknek
    Naknek is a small fishing community in southwestern Alaska known for its salmon canning industry and location near Bristol Bay.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c464fba881908d0ff2ac80511ce1 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef3bb0c42c8190997fbeb7a764d60e completed April 27, 2026, 10:34 a.m.
Created at: April 16, 2026, 6:34 p.m.