Triple

T19586776
Position Surface form Disambiguated ID Type / Status
Subject Bitwarden E490125 entity
Predicate supportsBrowser P5090 FINISHED
Object Opera NE NERFINISHED

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 | Statement: [Bitwarden, supportsBrowser, Opera]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Opera
Context triple: [Bitwarden, supportsBrowser, Opera]
  • A. Opera chosen
    Opera is a web browser known for its built-in features like a free VPN, ad blocker, and integrated messaging tools.
  • B. Opera
    Opera is a metro station on Cairo's Line 2 serving the downtown area near the Cairo Opera House and surrounding cultural landmarks.
  • C. Opera
    Opera is a historic Budapest Metro station located beneath Andrássy Avenue, serving the Hungarian State Opera House and the surrounding cultural district.
  • D. Ópera
    Ópera is a central Madrid Metro station located near the historic Teatro Real opera house and Plaza de Oriente.
  • E. OPERA
    OPERA was a long-baseline neutrino oscillation experiment at the Gran Sasso National Laboratory in Italy, designed to detect tau neutrinos in a beam sent from CERN.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8dd9374819098e36349b3211663 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e640523d10819091320a61456f6437 completed April 20, 2026, 3:03 p.m.
Created at: April 10, 2026, 1:42 p.m.