Triple
T32892004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruise Automation |
E841357
|
entity |
| Predicate | operatesFleetOf |
P72672
|
FINISHED |
| Object | self-driving cars |
—
|
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: self-driving cars | Statement: [Cruise Automation, operatesFleetOf, self-driving cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesFleetOf Context triple: [Cruise Automation, operatesFleetOf, self-driving cars]
-
A.
usesFleetOf
chosen
Indicates that one entity operates or relies on a group of vehicles, vessels, or similar assets collectively as a fleet to perform its activities or services.
-
B.
ownedFleet
Indicates that one entity possesses or controls a group of vehicles, vessels, or similar assets as its fleet.
-
C.
allCargoFleet
Indicates that the entire fleet or group in question consists exclusively of cargo-carrying units.
-
D.
operatesAircraftFor
Indicates that one entity pilots or controls an aircraft on behalf of, or in service to, another entity.
-
E.
homeFleet
Indicates that an entity serves as the primary or base fleet associated with another entity, such as a location, organization, or individual.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00332eaa0c8190a69ea895576bb0ee |
completed | May 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_6a0032b2ea80819083b89ebb88165933 |
completed | May 10, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:18 a.m.