Triple

T18758546
Position Surface form Disambiguated ID Type / Status
Subject Mount Nemrut E458710 entity
Predicate discoveredBy P412 FINISHED
Object Karl Sester
Karl Sester was a 19th-century German engineer and explorer best known for bringing the ancient monumental site of Mount Nemrut in Turkey to the attention of the archaeological world.
E2023219 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: Karl Sester | Statement: [Mount Nemrut, discoveredBy, Karl Sester]
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: Karl Sester
Triple: [Mount Nemrut, discoveredBy, Karl Sester]
Generated description
Karl Sester was a 19th-century German engineer and explorer best known for bringing the ancient monumental site of Mount Nemrut in Turkey to the attention of the archaeological world.

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_69d8d395dba0819087568404508590cb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e579f42d0881909bd9ca9c7916516a completed April 20, 2026, 12:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34b13b8adc81908ca1ea6c710b30c0 completed June 19, 2026, 3:02 a.m.
NEDg Description generation batch_6a34b1f2f6d4819082e910d0685eb95e completed June 19, 2026, 3:05 a.m.
NED2 Entity disambiguation (via description) batch_6a34b279c8688190b257df5ca22d7dd9 completed June 19, 2026, 3:07 a.m.
Created at: April 10, 2026, 11:52 a.m.