Triple
T9674602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School Improvement Grants |
E234115
|
entity |
| Predicate | subgrantee |
P63510
|
FINISHED |
| Object | local educational agencies |
—
|
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: local educational agencies | Statement: [School Improvement Grants, subgrantee, local educational agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subgrantee Context triple: [School Improvement Grants, subgrantee, local educational agencies]
-
A.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
B.
fundsCanBeSubgrantedTo
chosen
Indicates that funds received by one party are permitted to be passed on or reallocated as grants to another party.
-
C.
subsidiaryOrAsset
Indicates that one entity is owned, controlled, or held as a subsidiary company or asset by another entity.
-
D.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
E.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6d6dd48190a77c486337a58cb6 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.