Triple

T25922327
Position Surface form Disambiguated ID Type / Status
Subject Dallas, Pennsylvania E653203 entity
Predicate hasSchoolDistrict P226 FINISHED
Object Dallas School District
Dallas School District is a public school district serving students in and around the community of Dallas in northeastern Pennsylvania.
E1940626 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: Dallas School District | Statement: [Dallas, Pennsylvania, hasSchoolDistrict, Dallas School District]
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: Dallas School District
Triple: [Dallas, Pennsylvania, hasSchoolDistrict, Dallas School District]
Generated description
Dallas School District is a public school district serving students in and around the community of Dallas in northeastern Pennsylvania.

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_69e7ab3e025c819086771607157f0015 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f603ea6ea081909c6223c5544f6992 completed May 2, 2026, 2:02 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28fb843dc88190bc6b421c9ed6fde1 completed June 10, 2026, 5:52 a.m.
NEDg Description generation batch_6a28ffc3037481909e380c0b60ebce5c completed June 10, 2026, 6:10 a.m.
NED2 Entity disambiguation (via description) batch_6a29005bb6bc81909fa20caeb92ac2be completed June 10, 2026, 6:12 a.m.
Created at: April 22, 2026, 8:32 a.m.