Triple
T22369053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAFER barriers at Indianapolis Motor Speedway |
E552988
|
entity |
| Predicate | installedFor |
P147390
|
FINISHED |
| Object | driver protection |
—
|
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: driver protection | Statement: [SAFER barriers at Indianapolis Motor Speedway, installedFor, driver protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installedFor Context triple: [SAFER barriers at Indianapolis Motor Speedway, installedFor, driver protection]
-
A.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
B.
installedBy
Indicates that one entity was set up, put in place, or made operational through the actions or intervention of another entity.
-
C.
installedAfter
Indicates that one installation event occurred later in time than another installation event.
-
D.
installedInstrument
Indicates that one entity has placed or set up another entity as an instrument or device for use in a particular context or system.
-
E.
installedNear
Indicates that one entity is installed in physical proximity to another entity, typically within a short, functionally relevant distance.
- F. None of above. chosen
Provenance (4 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1580229688190a6e5e02b484033f7 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.