Triple
T16076296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PACER |
E389986
|
entity |
| Predicate | billingUnit |
P57372
|
FINISHED |
| Object | per page of data accessed |
—
|
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: per page of data accessed | Statement: [PACER, billingUnit, per page of data accessed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billingUnit Context triple: [PACER, billingUnit, per page of data accessed]
-
A.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
B.
budgetUnit
Indicates that one entity functions as the budgetary unit or cost-accounting unit associated with another entity within a financial or organizational context.
-
C.
billingMetric
chosen
Indicates a relationship where a specific metric or measure is used as the basis for calculating billing or charges between entities.
-
D.
billedBy
Indicates that one entity issues a bill or invoice to another entity for goods, services, or charges.
-
E.
billCharacteristic
Indicates that a bill possesses or is associated with a particular characteristic or attribute.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.