Triple

T25925626
Position Surface form Disambiguated ID Type / Status
Subject Bernice A. Ray Elementary School E653294 entity
Predicate namedAfter P63 FINISHED
Object Bernice A. Ray
Bernice A. Ray was an educator after whom the Bernice A. Ray Elementary School was named, recognizing her significant contributions to local education.
E1747926 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: Bernice A. Ray | Statement: [Bernice A. Ray Elementary School, namedAfter, Bernice A. Ray]
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: Bernice A. Ray
Triple: [Bernice A. Ray Elementary School, namedAfter, Bernice A. Ray]
Generated description
Bernice A. Ray was an educator after whom the Bernice A. Ray Elementary School was named, recognizing her significant contributions to local education.

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_69e7ab3eb9b881909c1390690551f868 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6041346c88190aa3d2c42b6e5ac5f completed May 2, 2026, 2:02 p.m.
NED1 Entity disambiguation (via context triple) batch_6a121e6db758819084bd693b4263dd84 completed May 23, 2026, 9:38 p.m.
NEDg Description generation batch_6a121f7b308c8190a2667f99b45cf2ab completed May 23, 2026, 9:43 p.m.
NED2 Entity disambiguation (via description) batch_6a1220284ddc819085b3ca2cad3fbfa9 completed May 23, 2026, 9:46 p.m.
Created at: April 22, 2026, 8:35 a.m.