Triple

T28932667
Position Surface form Disambiguated ID Type / Status
Subject Most Dangerous Man Alive E733828 entity
Predicate starring P1507 FINISHED
Object Richard Bakalyan
Richard Bakalyan was an American character actor known for his tough-guy roles in crime dramas and action films from the 1950s through the 1970s.
E1843081 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: Richard Bakalyan | Statement: [Most Dangerous Man Alive, starring, Richard Bakalyan]
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: Richard Bakalyan
Triple: [Most Dangerous Man Alive, starring, Richard Bakalyan]
Generated description
Richard Bakalyan was an American character actor known for his tough-guy roles in crime dramas and action films from the 1950s through the 1970s.

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_69f05b0b49b08190b8994b339c7980f6 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f65b539050819098dc3de1f083d23f completed May 2, 2026, 8:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24ec3df8e481908ce469268723a3e8 completed June 7, 2026, 3:57 a.m.
NEDg Description generation batch_6a24f741d0d08190932654cd45c92ec0 completed June 7, 2026, 4:44 a.m.
NED2 Entity disambiguation (via description) batch_6a24fafc00d481908d618fdc709806d6 completed June 7, 2026, 5 a.m.
Created at: April 28, 2026, 8:29 a.m.