Triple
T13097285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3120 |
E310622
|
entity |
| Predicate | supportsSpeakerphone |
P83515
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nokia 3120, supportsSpeakerphone, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSpeakerphone Context triple: [Nokia 3120, supportsSpeakerphone, yes]
-
A.
hasSpeakerphone
chosen
Indicates that an entity is equipped with or supports the use of a speakerphone function for audio communication.
-
B.
supportsVoIP
Indicates that one entity provides the capability for Voice over IP (VoIP) communication to or for another entity.
-
C.
haveRichVoiceSystem
Indicates that an entity possesses a voice system characterized by richness, such as depth, fullness, or expressive quality.
-
D.
hasVoiceSystem
Indicates that one entity possesses or is equipped with a particular voice-based system or voice technology.
-
E.
supportsConferenceCall
Indicates that one entity enables or is compatible with conducting a conference call involving multiple participants simultaneously.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9814e88a0819088418c792ce7aa57 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:04 p.m.