Triple
T405835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Model X |
E9380
|
entity |
| Predicate | infotainmentSystem |
P8159
|
FINISHED |
| Object | Tesla touchscreen interface |
—
|
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: Tesla touchscreen interface | Statement: [Tesla Model X, infotainmentSystem, Tesla touchscreen interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infotainmentSystem Context triple: [Tesla Model X, infotainmentSystem, Tesla touchscreen interface]
-
A.
musicVehicle
Indicates a relationship where a vehicle is associated with or used for playing, broadcasting, or producing music.
-
B.
offersInFlightEntertainment
Indicates that a service or provider makes entertainment options available to passengers during a flight.
-
C.
transportCharacteristic
chosen
Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
-
D.
hasOnboardComputer
Indicates that one entity is equipped with or contains an onboard computer system.
-
E.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbc00508190bbb602179273f29c |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e971a3a481909e6b075f25dd234a |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.