Triple
T27911140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Transportation Commission |
E705930
|
entity |
| Predicate | overseesFundingFor |
P48625
|
FINISHED |
| Object | Oregon’s transportation system |
—
|
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: Oregon’s transportation system | Statement: [Oregon Transportation Commission, overseesFundingFor, Oregon’s transportation system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesFundingFor Context triple: [Oregon Transportation Commission, overseesFundingFor, Oregon’s transportation system]
-
A.
fundingOversight
chosen
Indicates that one entity is responsible for monitoring, regulating, or supervising the use and allocation of funds provided to another entity.
-
B.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
C.
funderOf
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
D.
fundingFocus
Indicates that one entity’s funding is directed toward or prioritized for a particular target, theme, or area of activity.
-
E.
fundingComponent
Indicates that one entity serves as a financial contributor or funding source for another entity or activity.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 6:50 p.m.