Triple
T575366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android Auto |
E13750
|
entity |
| Predicate | primaryInputMethod |
P1302
|
FINISHED |
| Object | touchscreen |
—
|
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: touchscreen | Statement: [Android Auto, primaryInputMethod, touchscreen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInputMethod Context triple: [Android Auto, primaryInputMethod, touchscreen]
-
A.
primaryInterface
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
B.
inputDevice
Indicates that one entity functions as a device used to provide input to another entity or system.
-
C.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
D.
primaryMode
chosen
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
E.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b67395c8190a8046ff7debe9d1f |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c4969c819080375d08f9eec50c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.