Triple
T18302510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Service Fund |
E438389
|
entity |
| Predicate | disbursementMethod |
P9378
|
FINISHED |
| Object | support payments to eligible telecommunications carriers |
—
|
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: support payments to eligible telecommunications carriers | Statement: [Universal Service Fund, disbursementMethod, support payments to eligible telecommunications carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disbursementMethod Context triple: [Universal Service Fund, disbursementMethod, support payments to eligible telecommunications carriers]
-
A.
disbursementOption
chosen
Indicates the method or arrangement by which funds are paid out or distributed.
-
B.
methodOfSettlement
Indicates the way in which a transaction, obligation, or dispute is resolved, completed, or paid.
-
C.
disburses
Indicates the act of paying out or distributing funds or resources from a source to a recipient.
-
D.
beneficiarySelectionMethod
Indicates the way in which a beneficiary is chosen or determined in relation to an action, agreement, or resource.
-
E.
payType
Indicates the method or category of payment used in a transaction or compensation arrangement.
- 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.