Triple
T10883581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Highway Safety Plan |
E256983
|
entity |
| Predicate | targetsSystem |
P74097
|
FINISHED |
| Object | roadway 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: roadway transportation system | Statement: [Strategic Highway Safety Plan, targetsSystem, roadway transportation system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsSystem Context triple: [Strategic Highway Safety Plan, targetsSystem, roadway transportation system]
-
A.
targetsSystems
chosen
Indicates that an entity is directed at, attacks, or is intended to affect specific systems.
-
B.
targetsEcosystem
Indicates that an action, product, or policy is directed toward, affects, or is specifically intended for a particular ecosystem.
-
C.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
D.
targetFarmingSystem
Indicates a relationship where something is directed toward, designed for, or focused on a particular farming system.
-
E.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751dc3518819090e03d81ea5c8aa9 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.