Triple

T22374254
Position Surface form Disambiguated ID Type / Status
Subject Misko Hevery E553114 entity
Predicate givenName P17 FINISHED
Object Misko
Misko is a software engineer best known as the creator of the Angular web application framework.
 E1533296 NE FINISHED

How this triple was built (4 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: Misko | Statement: [Misko Hevery, givenName, Misko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Misko
Context triple: [Misko Hevery, givenName, Misko]
  • A. Milak
    Milak is a border town in India’s Uttar Pradesh state, known as a road-linked crossing point on the route to Afghanistan via Zaranj.
  • B. Mickoski
    Mickoski is a Macedonian surname most prominently associated with Hristijan Mickoski, a leading politician in North Macedonia.
  • C. Husák
    Husák is a Slovak surname most prominently associated with Gustáv Husák, the communist politician who served as president of Czechoslovakia during the normalization era.
  • D. Micka
    Micka is a diminutive or affectionate nickname commonly used for the given name Michael.
  • E. Milík
    Milík is a small village in southern Poland located within the administrative district of Gmina Muszyna in the Lesser Poland Voivodeship.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Misko
Triple: [Misko Hevery, givenName, Misko]
Generated description
Misko is a software engineer best known as the creator of the Angular web application framework.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Misko
Target entity description: Misko is a software engineer best known as the creator of the Angular web application framework.
  • A. Milak
    Milak is a border town in India’s Uttar Pradesh state, known as a road-linked crossing point on the route to Afghanistan via Zaranj.
  • B. Mickoski
    Mickoski is a Macedonian surname most prominently associated with Hristijan Mickoski, a leading politician in North Macedonia.
  • C. Husák
    Husák is a Slovak surname most prominently associated with Gustáv Husák, the communist politician who served as president of Czechoslovakia during the normalization era.
  • D. Micka
    Micka is a diminutive or affectionate nickname commonly used for the given name Michael.
  • E. Milík
    Milík is a small village in southern Poland located within the administrative district of Gmina Muszyna in the Lesser Poland Voivodeship.
  • F. None of above. chosen

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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15806b534819083716c2b090ede42 completed April 29, 2026, 12:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0ae06c2a5c8190a6f46e78ac762b58 completed May 18, 2026, 9:48 a.m.
NEDg Description generation batch_6a0ae37d53688190a8e4d17a2333f7ba completed May 18, 2026, 10:01 a.m.
NED2 Entity disambiguation (via description) batch_6a0ae414dd488190ac5dfa2418d9bd8b completed May 18, 2026, 10:04 a.m.
Created at: April 16, 2026, 8:45 p.m.