Triple
T18302683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Service Fund contributions from telecommunications providers |
E438393
|
entity |
| Predicate | mayBePassedThroughTo |
P93432
|
FINISHED |
| Object | end-user customers |
—
|
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: end-user customers | Statement: [Universal Service Fund contributions from telecommunications providers, mayBePassedThroughTo, end-user customers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBePassedThroughTo Context triple: [Universal Service Fund contributions from telecommunications providers, mayBePassedThroughTo, end-user customers]
-
A.
canBePassedTo
chosen
Indicates that one entity is capable of being transferred, handed over, or given to another entity.
-
B.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
C.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
-
D.
passesThroughState
Indicates that something (such as a route, path, or process) traverses or goes through a particular state or region during its course.
-
E.
supportsPassthrough
Indicates that one entity enables or allows another entity’s data, signals, or operations to pass through it unchanged.
- 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.