Triple
T28771361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vive Focus |
E726420
|
entity |
| Predicate | supportsContentStore |
P74462
|
FINISHED |
| Object | Viveport |
E1824298
|
NE 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: Viveport | Statement: [Vive Focus, supportsContentStore, Viveport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsContentStore Context triple: [Vive Focus, supportsContentStore, Viveport]
-
A.
supportsKeyStorage
Indicates that an entity is capable of securely storing cryptographic keys or similar sensitive key material.
-
B.
supportsBlockStorage
Indicates that one entity provides or is compatible with block-level storage capabilities for another entity.
-
C.
supportsOnlineContent
chosen
Indicates that one entity provides the infrastructure, functionality, or capability for another entity to host, deliver, or interact with content over the internet.
-
D.
supportsContentBrands
Indicates that one entity provides functionality, compatibility, or infrastructure necessary for the operation or distribution of specific content brands.
-
E.
supportsStoredValue
Indicates that an entity is capable of holding, managing, or processing stored monetary or credit value for later use.
- F. None of above.
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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a01d339feac8190a3de56b24db67163 |
completed | May 11, 2026, 1:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24a26586b48190b1a011bdecd38a46 |
completed | June 6, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_6a01d2bc1f408190a04869f95e6941ee |
completed | May 11, 2026, 12:59 p.m. |
Created at: April 28, 2026, 6:16 a.m.