Triple

T33921164
Position Surface form Disambiguated ID Type / Status
Subject Howard Winklevoss E869610 entity
Predicate employer P7 FINISHED
Object Winklevoss Consultants
Winklevoss Consultants is a consulting firm associated with actuary and academic Howard Winklevoss, known for its work in actuarial and pension-related advisory services.
E2072987 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: Winklevoss Consultants | Statement: [Howard Winklevoss, employer, Winklevoss Consultants]
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: Winklevoss Consultants
Triple: [Howard Winklevoss, employer, Winklevoss Consultants]
Generated description
Winklevoss Consultants is a consulting firm associated with actuary and academic Howard Winklevoss, known for its work in actuarial and pension-related advisory services.

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_69f349992c508190aa4afa24a086cc8c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f701eba5d48190854e10c68a6b4da7 completed May 3, 2026, 8:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a368251b7148190a82672a8e7d57ad6 completed June 20, 2026, 12:06 p.m.
NEDg Description generation batch_6a36833628008190be2fee19069cfad6 completed June 20, 2026, 12:10 p.m.
NED2 Entity disambiguation (via description) batch_6a36848f1d1881908bb386f2efd7e47a completed June 20, 2026, 12:16 p.m.
Created at: May 1, 2026, 1:49 a.m.