Triple
T17240705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6310 |
E418488
|
entity |
| Predicate | supportsVoiceCommands |
P11061
|
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: [Nokia 6310, supportsVoiceCommands, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVoiceCommands Context triple: [Nokia 6310, supportsVoiceCommands, true]
-
A.
hasVoiceSystem
Indicates that one entity possesses or is equipped with a particular voice-based system or voice technology.
-
B.
haveRichVoiceSystem
Indicates that an entity possesses a voice system characterized by richness, such as depth, fullness, or expressive quality.
-
C.
usesVoiceAssistant
Indicates that an entity regularly operates or interacts with a voice-controlled digital assistant.
-
D.
supportsCommand
chosen
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
E.
supportsVoIP
Indicates that one entity provides the capability for Voice over IP (VoIP) communication to or for 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e1f385c8190ae44e702923b6f66 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.