Triple

T28712510
Position Surface form Disambiguated ID Type / Status
Subject Carian alphabet E729865 entity
Predicate writingSystemFamily P9330 FINISHED
Object Anatolian scripts
Anatolian scripts are a group of ancient writing systems used in Anatolia to record various Anatolian languages, including Luwian, Lycian, and Carian.
E1830212 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: Anatolian scripts | Statement: [Carian alphabet, writingSystemFamily, Anatolian scripts]
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: Anatolian scripts
Triple: [Carian alphabet, writingSystemFamily, Anatolian scripts]
Generated description
Anatolian scripts are a group of ancient writing systems used in Anatolia to record various Anatolian languages, including Luwian, Lycian, and Carian.

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_69f043e7d5a4819094b18aca10b1e024 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f656d92c088190918720a02e2d923c completed May 2, 2026, 7:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1ccf5666d48190a5a54288bdbea1d2 completed June 1, 2026, 12:16 a.m.
NEDg Description generation batch_6a1cd021944881908cae19ba344f1184 completed June 1, 2026, 12:19 a.m.
NED2 Entity disambiguation (via description) batch_6a249457116881909199d0b381a902c3 completed June 6, 2026, 9:42 p.m.
Created at: April 28, 2026, 5:48 a.m.