Triple
T2456346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motor Carrier Safety Assistance Program |
E54429
|
entity |
| Predicate | emphasisArea |
P10883
|
FINISHED |
| Object | high-risk motor carriers |
—
|
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: high-risk motor carriers | Statement: [Motor Carrier Safety Assistance Program, emphasisArea, high-risk motor carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasisArea Context triple: [Motor Carrier Safety Assistance Program, emphasisArea, high-risk motor carriers]
-
A.
engagementArea
Indicates the spatial region or scope within which an entity’s actions, influence, or interactions are intended to occur.
-
B.
featuredArea
Indicates that an area or section is highlighted or given special prominence within a larger context or layout.
-
C.
targetArea
chosen
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
D.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
E.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.