Triple
T10852374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivaldi web browser |
E256179
|
entity |
| Predicate | stableReleaseModel |
P19968
|
FINISHED |
| Object | continuous |
—
|
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: continuous | Statement: [Vivaldi web browser, stableReleaseModel, continuous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stableReleaseModel Context triple: [Vivaldi web browser, stableReleaseModel, continuous]
-
A.
stableReleaseStatus
Indicates the release status or condition of a stable version of something (such as software or a product).
-
B.
stableReleaseInput
Indicates that an entity serves as the input or basis for determining a stable (official) release version of another entity.
-
C.
hasReleaseModel
chosen
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
D.
stableReleasesMaintainedBy
Indicates that the stable (non-development) releases of a software project are currently being maintained or supported by a particular entity.
-
E.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75117b76c8190b0fb216b1428c3c7 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.