Triple

T21061765
Position Surface form Disambiguated ID Type / Status
Subject Furst–Saxe–Sipser lower bounds E518865 entity
Predicate namedAfter P63 FINISHED
Object James B. Saxe
James B. Saxe is a theoretical computer scientist known for his contributions to computational complexity, including work leading to the Furst–Saxe–Sipser lower bounds.
E2054702 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: James B. Saxe | Statement: [Furst–Saxe–Sipser lower bounds, namedAfter, James B. Saxe]
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: James B. Saxe
Triple: [Furst–Saxe–Sipser lower bounds, namedAfter, James B. Saxe]
Generated description
James B. Saxe is a theoretical computer scientist known for his contributions to computational complexity, including work leading to the Furst–Saxe–Sipser lower bounds.

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_69e0b505ef108190b25dd4033e2ff7eb completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6feb064a48190b892b78e27e8d0fa completed April 21, 2026, 4:36 a.m.
NED1 Entity disambiguation (via context triple) batch_6a35a64b23ec8190938f1ae72efbec59 completed June 19, 2026, 8:27 p.m.
NEDg Description generation batch_6a35a6bf0bb08190878fe21fa3c6d5ea completed June 19, 2026, 8:29 p.m.
NED2 Entity disambiguation (via description) batch_6a35a731ae0c8190a71409322d9c5ad0 completed June 19, 2026, 8:31 p.m.
Created at: April 16, 2026, 2:38 p.m.