Triple
T28771382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vive Focus |
E726420
|
entity |
| Predicate | supportsDeveloperSDK |
P125228
|
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, supportsDeveloperSDK, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeveloperSDK Context triple: [Vive Focus, supportsDeveloperSDK, yes]
-
A.
supportsDeveloper
Indicates that one entity provides assistance, resources, or advocacy to help a developer perform their work or achieve their goals.
-
B.
hasSoftwareDevelopmentKit
chosen
Indicates that an entity provides or is associated with a software development kit (SDK) that can be used to develop, integrate, or extend its functionality.
-
C.
supportsAPIClientSDKs
Indicates that an entity provides or is compatible with software development kits (SDKs) intended for use by API clients.
-
D.
supportsDebuggingTools
Indicates that an entity provides or is compatible with tools used for debugging or diagnosing issues.
-
E.
hasDevelopmentDriver
Indicates that one entity serves as a driving factor, cause, or motivator for the development, growth, or advancement of another entity.
- 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_6a01ed1790148190b08c1dba53de4371 |
completed | May 11, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_6a01e9c20798819085760b377dc7b3fa |
completed | May 11, 2026, 2:37 p.m. |
Created at: April 28, 2026, 6:16 a.m.