Triple
T24396673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OnStar Safety & Security |
E615044
|
entity |
| Predicate | availabilityNote |
P156048
|
FINISHED |
| Object | where available |
—
|
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: where available | Statement: [OnStar Safety & Security, availabilityNote, where available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availabilityNote Context triple: [OnStar Safety & Security, availabilityNote, where available]
-
A.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
B.
availabilityType
Indicates the specific way in which something is available or offered (e.g., its mode, status, or conditions of availability) in relation to another entity.
-
C.
availabilityModel
Indicates how and under what conditions an entity is available for use, access, or interaction.
-
D.
availabilityStatus
Indicates the current state of whether something is obtainable, usable, or accessible at a given time.
-
E.
availabilityEnd
Indicates the point in time or condition after which something is no longer available or offered.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294d79dac8190bb79519f4aed91f2 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:04 a.m.