Triple
T9106098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford BlueCruise |
E218480
|
entity |
| Predicate | softwareUpdatable |
P87181
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ford BlueCruise, softwareUpdatable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareUpdatable Context triple: [Ford BlueCruise, softwareUpdatable, true]
-
A.
softwareUpdateModel
Indicates that one entity serves as the model, specification, or type definition used to perform or describe a software update on another entity.
-
B.
upgradeEligibility
Indicates whether an entity qualifies to move from its current version, level, or plan to a higher or more advanced one under defined criteria.
-
C.
supportsOneClickUpdates
Indicates that an entity enables or is compatible with performing updates through a streamlined, single-action (one-click) process.
-
D.
unveiledSoftwareUpdate
Indicates that an entity has publicly revealed or announced a new or updated version of a software product.
-
E.
requiresUpdate
Indicates that an entity must be refreshed, modified, or brought to a newer state before it can be considered current or valid.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca57286a88190b256d2461c5c0aed |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:16 p.m.