Triple

T34606307
Position Surface form Disambiguated ID Type / Status
Subject Yugoslav Partisan Supreme Headquarters E888602 entity
Predicate hasMember P10 FINISHED
Object Petar Drapšin
Petar Drapšin was a prominent Yugoslav Partisan commander during World War II who later became a general in the Yugoslav People's Army.
E2162870 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: Petar Drapšin | Statement: [Yugoslav Partisan Supreme Headquarters, hasMember, Petar Drapšin]
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: Petar Drapšin
Triple: [Yugoslav Partisan Supreme Headquarters, hasMember, Petar Drapšin]
Generated description
Petar Drapšin was a prominent Yugoslav Partisan commander during World War II who later became a general in the Yugoslav People's Army.

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_69f349d489d48190ba30e7d97c6f5ef9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f721c1b1ec819086397109822870ef completed May 3, 2026, 10:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a38b6db00308190a179c26f2725d2b8 completed June 22, 2026, 4:15 a.m.
NEDg Description generation batch_6a38b844a3d88190b5bfc7797cc3c276 completed June 22, 2026, 4:21 a.m.
NED2 Entity disambiguation (via description) batch_6a38b8872e40819089a03fcdd538f04b completed June 22, 2026, 4:22 a.m.
Created at: May 1, 2026, 2:03 a.m.