Triple

T35064552
Position Surface form Disambiguated ID Type / Status
Subject Gökdepe E1011690 entity
Predicate regionCapitalOf P204 FINISHED
Object Gökdepe District
Gökdepe District is an administrative district in Ahal Province of central Turkmenistan, known for its historical significance and proximity to the capital city, Ashgabat.
E2148784 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: Gökdepe District | Statement: [Gökdepe, regionCapitalOf, Gökdepe District]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Gökdepe District
Triple: [Gökdepe, regionCapitalOf, Gökdepe District]
Generated description
Gökdepe District is an administrative district in Ahal Province of central Turkmenistan, known for its historical significance and proximity to the capital city, Ashgabat.

Provenance (5 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_69f76dd09c308190a523454853ce842b completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78611cef081908cf99c196df5b068 completed May 3, 2026, 5:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38682e25348190bed03618371f6dd9 completed June 21, 2026, 10:39 p.m.
NEDg Description generation batch_6a3868e166b481909f20c50f68068dd8 completed June 21, 2026, 10:42 p.m.
NED2 Entity disambiguation (via description) batch_6a3869318bb08190a83698102b8d16bf completed June 21, 2026, 10:44 p.m.
Created at: May 3, 2026, 4:01 p.m.