Triple
T13125926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android 10 |
E311842
|
entity |
| Predicate | UIChange |
P31366
|
FINISHED |
| Object | gesture-based system navigation |
—
|
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: gesture-based system navigation | Statement: [Android 10, UIChange, gesture-based system navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UIChange Context triple: [Android 10, UIChange, gesture-based system navigation]
-
A.
notableGUIChange
chosen
Indicates a significant modification or redesign in a system’s graphical user interface compared to its previous state.
-
B.
surfaceChange
Indicates a change in the physical surface characteristics or condition of an entity over time or due to some event or interaction.
-
C.
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.
-
D.
namespaceChangedTo
Indicates that an entity’s namespace has been updated or reassigned from its previous value to a new one.
-
E.
functionChange
Indicates that an entity’s function, role, or operational behavior has been altered from one state or purpose to another.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819946808190b41335fb1054accd |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.