Triple
T9589615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highway Safety Improvement Program |
E231382
|
entity |
| Predicate | eligibleProjects |
P15180
|
FINISHED |
| Object | infrastructure safety projects |
—
|
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: infrastructure safety projects | Statement: [Highway Safety Improvement Program, eligibleProjects, infrastructure safety projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleProjects Context triple: [Highway Safety Improvement Program, eligibleProjects, infrastructure safety projects]
-
A.
eligibleProject
chosen
Indicates that a project satisfies the required conditions or criteria to qualify for a particular status, process, or benefit.
-
B.
eligibleProjectType
Indicates that a project belongs to a category or type that qualifies it for a specific program, process, or benefit.
-
C.
eligibleWorks
Indicates that certain works meet the required criteria or conditions to qualify for a specified status, use, or consideration.
-
D.
eligibleWork
Indicates that a particular work satisfies the necessary conditions or criteria to qualify for a specified status, benefit, or consideration.
-
E.
intendedProject
Indicates that an entity is the planned or targeted project associated with another entity (such as a person, organization, 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99f1696c8190addf1a43544f2c18 |
completed | April 1, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.