Triple
T2207252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opera |
E50828
|
entity |
| Predicate | hasMobileVersion |
P14571
|
FINISHED |
| Object | Opera Mini |
E50829
|
NE 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 Mini | Statement: [Opera, hasMobileVersion, Opera Mini]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Opera Mini Context triple: [Opera, hasMobileVersion, Opera Mini]
-
A.
Opera Mini
chosen
Opera Mini is a lightweight mobile web browser designed to compress data and load pages quickly, especially on slower networks and lower-end devices.
-
B.
UR Browser
UR Browser is a Chromium-based web browser focused on user privacy, security, and customization features.
-
C.
Colibri Browser
Colibri Browser is a minimalist web browser focused on speed and simplicity, built on the Blink rendering engine.
-
D.
Kinza Browser
Kinza Browser is a Japanese-developed, Chromium-based web browser that offers extensive customization options and user-centric features built on the Blink rendering engine.
-
E.
Epic Privacy Browser
Epic Privacy Browser is a Chromium-based web browser focused on protecting user privacy through built-in ad and tracker blocking, encrypted proxy, and minimal data collection.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc5b101d48190a321625720d537b6 |
completed | March 7, 2026, 6:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae654b89b081908f8c8b9bfc0b6579 |
completed | March 9, 2026, 6:14 a.m. |
Created at: March 4, 2026, 7:46 p.m.