Triple
T6009957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opera (Chromium-based) |
E133805
|
entity |
| Predicate | supportsAccount |
P15674
|
FINISHED |
| Object | Opera account |
—
|
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: Opera account | Statement: [Opera (Chromium-based), supportsAccount, Opera account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAccount Context triple: [Opera (Chromium-based), supportsAccount, Opera account]
-
A.
supportsAccountType
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
B.
supportedAct
Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
-
C.
supportsOrganization
Indicates that one entity provides assistance, resources, or advocacy that helps sustain or advance an organization.
-
D.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
-
E.
supportsOnlineAccountManagement
chosen
Indicates that an entity provides functionality for users to manage their accounts through an online interface or platform.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f4e27a881909cc3f7fef62abc3b |
completed | March 22, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.