Triple

T28817016
Position Surface form Disambiguated ID Type / Status
Subject Foltz E727664 entity
Predicate hasNotableBearer P458 FINISHED
Object Jonathan Foltz
Jonathan Foltz is a notable individual recognized as a bearer of the Foltz surname, though specific widely known public details about his life or work are not clearly established.
E1853289 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: Jonathan Foltz | Statement: [Foltz, hasNotableBearer, Jonathan Foltz]
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: Jonathan Foltz
Triple: [Foltz, hasNotableBearer, Jonathan Foltz]
Generated description
Jonathan Foltz is a notable individual recognized as a bearer of the Foltz surname, though specific widely known public details about his life or work are not clearly established.

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_69f0319d09088190bbf14cdf1987792a completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f658f44774819090ba520d0d95c6be completed May 2, 2026, 8:05 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25503a2d70819080c564fb3d34304c completed June 7, 2026, 11:04 a.m.
NEDg Description generation batch_6a25547c1cb881909b0a85b2bb6d61f1 completed June 7, 2026, 11:22 a.m.
NED2 Entity disambiguation (via description) batch_6a2558d26f808190b01d391c806b780d completed June 7, 2026, 11:41 a.m.
Created at: April 28, 2026, 6:33 a.m.