Triple
T28771380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vive Focus |
E726420
|
entity |
| Predicate | supportsExternalHeadphones |
P117474
|
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: [Vive Focus, supportsExternalHeadphones, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsExternalHeadphones Context triple: [Vive Focus, supportsExternalHeadphones, yes]
-
A.
supports3_5mmJack
chosen
Indicates that one entity is compatible with or provides a 3.5mm audio jack connection for another entity.
-
B.
supportsAudioReturnChannel
Indicates that one entity is capable of handling an audio return channel from another entity, allowing audio to be sent back over the same connection.
-
C.
supportsBluetoothCodec
Indicates that one entity is capable of using or is compatible with a specified Bluetooth audio codec in its operation or communication.
-
D.
supportsAudioEnhancement
Indicates that one entity provides or enables audio enhancement capabilities for another entity or process.
-
E.
supportsLightningEarPods
Indicates that one entity is compatible with and can be used with Lightning-connector EarPods.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a01e993fec0819090cc397218515e88 |
completed | May 11, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_6a01e57594188190a2354f48cf71b48c |
completed | May 11, 2026, 2:19 p.m. |
Created at: April 28, 2026, 6:16 a.m.