Triple
T37282863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acton Middle School |
E925444
|
entity |
| Predicate | hasLevelWithinDistrict |
P176124
|
FINISHED |
| Object | secondary school |
—
|
LITERAL 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: secondary school | Statement: [Acton Middle School, hasLevelWithinDistrict, secondary school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelWithinDistrict Context triple: [Acton Middle School, hasLevelWithinDistrict, secondary school]
-
A.
belongsToDistrictLevelCity
Indicates that an entity is administratively part of, or falls under the jurisdiction of, a specific district-level city.
-
B.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
C.
hasLocalDistrict
Indicates that an entity is associated with or falls under the jurisdiction of a specific local administrative district.
-
D.
withinDistrictType
chosen
Indicates that one entity is located inside or falls under the jurisdiction of a specific type or category of district.
-
E.
meetsInDistrict
Indicates that two or more entities hold a meeting within the boundaries of a specified administrative district.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:16 p.m.