Triple
T14420706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android One |
E357575
|
entity |
| Predicate | updateControl |
P90840
|
FINISHED |
| Object | Google manages core software updates |
—
|
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: Google manages core software updates | Statement: [Android One, updateControl, Google manages core software updates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateControl Context triple: [Android One, updateControl, Google manages core software updates]
-
A.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
B.
modificationControl
chosen
Indicates that one entity has the authority or capability to alter, update, or otherwise change another entity or its properties.
-
C.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
D.
updateProcess
Indicates the action or procedure by which an existing item, system, or state is modified to a newer or revised version.
-
E.
updateSource
Indicates that one entity serves as the origin or provider of information, data, or content used to modify or refresh another 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de910eb354819089d5d5a46919eb49 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.