Triple
T136302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruise LLC |
E2753
|
entity |
| Predicate | safetyApproach |
P2368
|
FINISHED |
| Object | redundant sensing and computing systems |
—
|
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: redundant sensing and computing systems | Statement: [Cruise LLC, safetyApproach, redundant sensing and computing systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyApproach Context triple: [Cruise LLC, safetyApproach, redundant sensing and computing systems]
-
A.
policyApproach
Indicates the strategy, method, or overall course of action adopted in creating, implementing, or managing a policy.
-
B.
managementApproach
Indicates the strategy, methods, or style used to direct, organize, and oversee the activities or resources of an entity or process.
-
C.
securityAspect
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
-
D.
securityFeature
chosen
Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
-
E.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a4edf081908c494c8370c76b9a |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25651b9048190a6277b7fec98c1ea |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.