Triple
T14447794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chromium rendering engine |
E358251
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | Opera |
E72095
|
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 | Statement: [Chromium rendering engine, usedBy, Opera]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Opera Context triple: [Chromium rendering engine, usedBy, Opera]
-
A.
Opera
Opera is a metro station on Cairo's Line 2 serving the downtown area near the Cairo Opera House and surrounding cultural landmarks.
-
B.
Opera
chosen
Opera is a web browser known for its built-in features like a free VPN, ad blocker, and integrated messaging tools.
-
C.
Ópera
Ópera is a central Madrid Metro station located near the historic Teatro Real opera house and Plaza de Oriente.
-
D.
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.
-
E.
Opéra
Opéra is a major Paris Métro station and transport hub located near the Palais Garnier in central Paris.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9160126c8190a2862a1a3dde1aff |
completed | April 14, 2026, 7:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bdf451c8190baaa3f7500eaea16 |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:19 a.m.