Triple
T33603392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opera Link |
E860779
|
entity |
| Predicate | endOfLifeAction |
P178657
|
FINISHED |
| Object | migration to Opera Sync |
—
|
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: migration to Opera Sync | Statement: [Opera Link, endOfLifeAction, migration to Opera Sync]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfLifeAction Context triple: [Opera Link, endOfLifeAction, migration to Opera Sync]
-
A.
endOfLife
Indicates that an entity has reached the termination point of its existence, lifecycle, or functional use.
-
B.
endOfLifeReason
Indicates the cause, circumstance, or justification for why an entity’s existence, validity, or lifecycle has come to an end.
-
C.
endOfLifeDate
Indicates the date on which an entity’s existence, validity, or operational life comes to an end.
-
D.
endOfExtendedSupport
Indicates the point in time when extended support for something (such as a product or service) is officially terminated.
-
E.
endOfSupportAppliesTo
Indicates that a specific end-of-support status or policy is applicable to a particular product, service, or component.
- F. None of above. chosen
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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f713bfdc148190a249a7874320bab8 |
completed | May 3, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f7135fa2988190a20a94cfe616d754 |
completed | May 3, 2026, 9:20 a.m. |
Created at: May 1, 2026, 1:41 a.m.