Triple
T27111673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herndon area of Fairfax County, Virginia |
E686728
|
entity |
| Predicate | hasLocalHighSchool |
P113
|
FINISHED |
| Object | Herndon High School |
—
|
NE NERFINISHED |
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: Herndon High School | Statement: [Herndon area of Fairfax County, Virginia, hasLocalHighSchool, Herndon High School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalHighSchool Context triple: [Herndon area of Fairfax County, Virginia, hasLocalHighSchool, Herndon High School]
-
A.
attendedHighSchoolIn
Indicates that an entity completed or was enrolled in high school education in a specified location.
-
B.
hasSchool
chosen
Indicates that an entity possesses, is associated with, or is served by a particular school.
-
C.
hasSingleHighSchool
Indicates that an entity is associated with exactly one high school.
-
D.
hasNotableHighSchool
Indicates that an entity is associated with a high school that is particularly notable or significant in some recognized way.
-
E.
hasSchoolIn
Indicates that a school is located within or operates in a specified place or region.
- F. None of above.
Provenance (3 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 8:54 a.m.