Triple

T12158963
Position Surface form Disambiguated ID Type / Status
Subject Sanming E289653 entity
Predicate borderedBy P224 FINISHED
Object Longyan E294939 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: Longyan | Statement: [Sanming, borderedBy, Longyan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Longyan
Context triple: [Sanming, borderedBy, Longyan]
  • A. Longyan chosen
    Longyan is a prefecture-level city in western Fujian Province, China, known for its Hakka culture, mountainous landscapes, and historic tulou earthen dwellings.
  • B. Nanping
    Nanping is a prefecture-level city in northern Fujian Province, China, known for its mountainous terrain, rich biodiversity, and role as a regional transport and economic hub.
  • C. Xianning
    Xianning is a prefecture-level city in southeastern Hubei Province, China, known for its hot springs, karst landscapes, and historical sites.
  • D. Sanming
    Sanming is a prefecture-level industrial and transport hub located in the mountainous interior of Fujian Province in southeastern China.
  • E. Zunhua City
    Zunhua City is a county-level city in northeastern Hebei Province, China, known for its historical sites and administrative affiliation with the prefecture-level city of Tangshan.
  • 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_69d6ab4c6710819097a9d228382dde43 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915c277e481908351bf4e664dda42 completed April 10, 2026, 3:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65e9868ec81909efd7e142d5fb090 completed May 2, 2026, 8:29 p.m.
Created at: April 8, 2026, 9:50 p.m.