Triple
T13625222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uber Advanced Technologies Group |
E325559
|
entity |
| Predicate | developedComponent |
P81035
|
FINISHED |
| Object | lidar 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: lidar systems | Statement: [Uber Advanced Technologies Group, developedComponent, lidar systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedComponent Context triple: [Uber Advanced Technologies Group, developedComponent, lidar systems]
-
A.
developsComponentFor
Indicates that one entity creates or builds a component intended to be used by or within another entity.
-
B.
hasComponentDevelopment
chosen
Indicates that an entity is involved in or responsible for the development of one or more of its components.
-
C.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
D.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
E.
developedUnder
Indicates that something was created, produced, or brought into existence while being subject to the authority, guidance, or conditions imposed by a particular person, organization, regime, or framework.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:50 p.m.