Triple
T28771371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vive Focus |
E726420
|
entity |
| Predicate | supportsStandaloneOperation |
P97184
|
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, supportsStandaloneOperation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStandaloneOperation Context triple: [Vive Focus, supportsStandaloneOperation, yes]
-
A.
isStandaloneFriendly
chosen
Indicates that an entity can operate or be used effectively on its own without requiring integration or support from other entities.
-
B.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
C.
supportsOperationsWith
Indicates that one entity enables, facilitates, or is compatible with the execution of operations involving another entity.
-
D.
isStandaloneWork
Indicates that a work exists independently and is not part of a larger series, collection, or multi-part work.
-
E.
operationSupported
Indicates that a particular operation is available and can be performed or handled by a given entity or system.
- 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_6a01d48f41f4819093a5b47288a073c1 |
completed | May 11, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_6a01d3fa278c8190838174dd96ef5dde |
completed | May 11, 2026, 1:04 p.m. |
Created at: April 28, 2026, 6:16 a.m.