Triple
T18302570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FCC Form 470 |
E438390
|
entity |
| Predicate | hasEligibilityScope |
P24457
|
FINISHED |
| Object | E-Rate eligible services only |
—
|
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: E-Rate eligible services only | Statement: [FCC Form 470, hasEligibilityScope, E-Rate eligible services only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEligibilityScope Context triple: [FCC Form 470, hasEligibilityScope, E-Rate eligible services only]
-
A.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
B.
eligibilityContext
chosen
Indicates the situational or conditional factors under which an entity qualifies for or is considered eligible for something.
-
C.
hasRecognitionScope
Indicates the extent or context within which a recognition, award, or acknowledgment is valid or applies.
-
D.
eligibilityArea
Indicates that a specified geographic or conceptual area defines where something (such as a person, item, or activity) is eligible or permitted.
-
E.
hasScopeRule
Indicates that a given entity is governed, constrained, or interpreted according to a particular scope-defining rule.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50180ac48819090e9a8f11ba10c3d |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.