Triple
T21224381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Term Evolution for Machines |
E523052
|
entity |
| Predicate | supportsVoice |
P59152
|
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: [Long Term Evolution for Machines, supportsVoice, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVoice Context triple: [Long Term Evolution for Machines, supportsVoice, true]
-
A.
supportsVoiceDialing
Indicates that one entity enables or is compatible with initiating phone calls through voice commands for another entity.
-
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
chosen
Indicates that one entity possesses or is equipped with a particular voice-based system or voice technology.
-
E.
supportsVoiceControlVia
Indicates that one entity provides or enables voice control functionality through another specified entity or mechanism.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734a9c9f88190817b574f916886e5 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.