Triple
T1037240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highway Trust Fund |
E22390
|
entity |
| Predicate | primaryRevenueSource |
P7220
|
FINISHED |
| Object | federal motor fuel excise taxes |
—
|
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: federal motor fuel excise taxes | Statement: [Highway Trust Fund, primaryRevenueSource, federal motor fuel excise taxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRevenueSource Context triple: [Highway Trust Fund, primaryRevenueSource, federal motor fuel excise taxes]
-
A.
majorRevenueSource
chosen
Indicates that one entity serves as the primary or dominant source of revenue for another entity.
-
B.
revenueSources
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
C.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
D.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
E.
revenueUse
Indicates how generated revenue is allocated, spent, or applied toward specific purposes or activities.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.