Triple
T21831017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple A9 |
E538993
|
entity |
| Predicate | supportsAlwaysOnHeySiri |
P145463
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Apple A9, supportsAlwaysOnHeySiri, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAlwaysOnHeySiri Context triple: [Apple A9, supportsAlwaysOnHeySiri, true]
-
A.
supportsVoiceControlVia
Indicates that one entity provides or enables voice control functionality through another specified entity or mechanism.
-
B.
haveRichVoiceSystem
Indicates that an entity possesses a voice system characterized by richness, such as depth, fullness, or expressive quality.
-
C.
hasVoiceSystem
Indicates that one entity possesses or is equipped with a particular voice-based system or voice technology.
-
D.
wakeWord
Indicates that one entity serves as the activation phrase or trigger word used to wake up or activate another entity (such as a device or system).
-
E.
supportsVoiceDialing
Indicates that one entity enables or is compatible with initiating phone calls through voice commands for another entity.
- F. None of above. chosen
Provenance (4 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f091362d9081909f00ad7a2806d5cb |
completed | April 28, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 6:55 p.m.