Triple

T32209410
Position Surface form Disambiguated ID Type / Status
Subject Anatolian Neolithic E822758 entity
Predicate hasSite P1205 FINISHED
Object Barcın Höyük
Barcın Höyük is an important early Neolithic archaeological mound in northwestern Turkey that has yielded some of the earliest evidence of farming and settled life in Anatolia.
E2006483 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: Barcın Höyük | Statement: [Anatolian Neolithic, hasSite, Barcın Höyük]
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: Barcın Höyük
Triple: [Anatolian Neolithic, hasSite, Barcın Höyük]
Generated description
Barcın Höyük is an important early Neolithic archaeological mound in northwestern Turkey that has yielded some of the earliest evidence of farming and settled life in Anatolia.

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_69f3490a3bec819097bc58d4731b9d08 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bb90bb908190a7b01f36dc123cf1 completed May 3, 2026, 3:05 a.m.
NED1 Entity disambiguation (via context triple) batch_6a344ef5b9d08190b9fc1aaf004f31ec completed June 18, 2026, 8:03 p.m.
NEDg Description generation batch_6a344f6dd14c8190ae8aa017de0e1e32 completed June 18, 2026, 8:05 p.m.
NED2 Entity disambiguation (via description) batch_6a345d3add6481909df61eb0d76be08b completed June 18, 2026, 9:03 p.m.
Created at: May 1, 2026, 12:37 a.m.