Triple

T35280631
Position Surface form Disambiguated ID Type / Status
Subject Bob Layton E1018923 entity
Predicate coCreated P1858 FINISHED
Object Bethany Cabe
Bethany Cabe is a Marvel Comics character closely associated with Iron Man, known as a skilled security specialist, bodyguard, and one of Tony Stark’s significant love interests.
E2133475 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: Bethany Cabe | Statement: [Bob Layton, coCreated, Bethany Cabe]
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: Bethany Cabe
Triple: [Bob Layton, coCreated, Bethany Cabe]
Generated description
Bethany Cabe is a Marvel Comics character closely associated with Iron Man, known as a skilled security specialist, bodyguard, and one of Tony Stark’s significant love interests.

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_69f76de6d39c8190bb11342e4b91ff2b completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78fd98d2881908009a11f3c4369c7 completed May 3, 2026, 6:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a380fc1146c8190a05baba52431a2c1 completed June 21, 2026, 4:22 p.m.
NEDg Description generation batch_6a38103cb2f88190ba2ca16db97ff04e completed June 21, 2026, 4:24 p.m.
NED2 Entity disambiguation (via description) batch_6a3811c18dbc8190936d4078136c12db completed June 21, 2026, 4:30 p.m.
Created at: May 3, 2026, 4:03 p.m.