Triple
T17669770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FCC Form 471 |
E440487
|
entity |
| Predicate | dataCollectedUsedFor |
P399
|
FINISHED |
| Object | calculating E-Rate funding commitments |
—
|
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: calculating E-Rate funding commitments | Statement: [FCC Form 471, dataCollectedUsedFor, calculating E-Rate funding commitments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectedUsedFor Context triple: [FCC Form 471, dataCollectedUsedFor, calculating E-Rate funding commitments]
-
A.
dataUse
chosen
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
B.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
C.
collectsDataFor
Indicates that one entity gathers or records data on behalf of, or for the benefit of, another entity.
-
D.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
E.
dataReportedBy
Indicates that certain data has been provided, recorded, or communicated by a specific source or reporting entity.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f67f6188190a978c7c9f462064d |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:59 a.m.