Triple

T28454100
Position Surface form Disambiguated ID Type / Status
Subject Beavercreek City School District E716659 entity
Predicate operates P24 FINISHED
Object Parkwood Elementary School
Parkwood Elementary School is a public primary school serving early-grade students in the Beavercreek, Ohio area.
E1821135 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: Parkwood Elementary School | Statement: [Beavercreek City School District, operates, Parkwood Elementary School]
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: Parkwood Elementary School
Triple: [Beavercreek City School District, operates, Parkwood Elementary School]
Generated description
Parkwood Elementary School is a public primary school serving early-grade students in the Beavercreek, Ohio area.

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_69efd6b76f8c8190a7ba908aca280942 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f64e7475308190b2e0b49d5f239539 completed May 2, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cac3d8cd8819093129de4bae99382 completed May 31, 2026, 9:46 p.m.
NEDg Description generation batch_6a1cac9b7c088190972eb6d682ce1c73 completed May 31, 2026, 9:48 p.m.
NED2 Entity disambiguation (via description) batch_6a1cad27e5e48190b2f917c1a51965e0 completed May 31, 2026, 9:50 p.m.
Created at: April 28, 2026, 1:53 a.m.