Triple

T30234111
Position Surface form Disambiguated ID Type / Status
Subject Douglas G. Grafflin Elementary School E768710 entity
Predicate namedAfter P63 FINISHED
Object Douglas G. Grafflin
Douglas G. Grafflin was an individual significant enough in his community or field that an elementary school was named in his honor.
E2289932 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: Douglas G. Grafflin | Statement: [Douglas G. Grafflin Elementary School, namedAfter, Douglas G. Grafflin]
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: Douglas G. Grafflin
Triple: [Douglas G. Grafflin Elementary School, namedAfter, Douglas G. Grafflin]
Generated description
Douglas G. Grafflin was an individual significant enough in his community or field that an elementary school was named in his honor.

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_69f224820c048190b1435c4cc145acf1 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68048f7e481908c7b6e3788b04549 completed May 2, 2026, 10:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5b7eca7db481909334fa26c1ca20a6 completed July 18, 2026, 1:25 p.m.
NEDg Description generation batch_6a5b7f3fca34819094c8bc80af4243e5 completed July 18, 2026, 1:27 p.m.
NED2 Entity disambiguation (via description) batch_6a5b7f95cff081909a1c308ce062ccc0 completed July 18, 2026, 1:28 p.m.
Created at: April 29, 2026, 7:37 p.m.