Triple

T14401546
Position Surface form Disambiguated ID Type / Status
Subject Ludian E357083 entity
Predicate hasDialects P4251 FINISHED
Object Northern Ludian E357082 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: Northern Ludian | Statement: [Ludian, hasDialects, Northern Ludian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Northern Ludian
Context triple: [Ludian, hasDialects, Northern Ludian]
  • A. Northern Ludian chosen
    Northern Ludian is a regional dialect of the Ludian language spoken by a subset of the Ludian-speaking community in northern areas of its range.
  • B. Southern Ludian
    Southern Ludian is a regional dialect of the Ludian language spoken by a subset of the Ludian-speaking community.
  • C. Central Ludian
    Central Ludian is a primary dialect of the Ludian language spoken by Ludian communities in northwestern Russia.
  • D. Northern Tai
    Northern Tai is a branch of the Tai language family spoken primarily in southern China and neighboring regions, distinct from but related to the Southwestern Tai languages.
  • E. Northern Lau
    Northern Lau is a dialectal variety of the Lau language spoken on Malaita in the Solomon Islands, distinguished by its own phonological and lexical features.
  • 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_69d827927c988190ad98bb0360981783 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de908500048190bb6a20fe318d5c62 completed April 14, 2026, 7:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5520c07c8190bfdaf224dd779ced completed May 8, 2026, 3:14 a.m.
Created at: April 10, 2026, 1:17 a.m.