Triple
T575359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android Auto |
E13750
|
entity |
| Predicate | requiresOperatingSystemVersion |
P11910
|
FINISHED |
| Object | Android 5.0 Lollipop or higher |
—
|
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: Android 5.0 Lollipop or higher | Statement: [Android Auto, requiresOperatingSystemVersion, Android 5.0 Lollipop or higher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresOperatingSystemVersion Context triple: [Android Auto, requiresOperatingSystemVersion, Android 5.0 Lollipop or higher]
-
A.
operatingSystem
Indicates that one entity is the operating system running on, or used by, another entity.
-
B.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
C.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
D.
requiresSoftware
chosen
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
-
E.
compatibilityNote
Indicates that there is an explanatory note or comment about how well two entities are compatible or work together.
- 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.