Triple
T12843038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | npower Championship |
E307100
|
entity |
| Predicate | sponsor |
P67
|
FINISHED |
| Object | npower |
E1006038
|
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: npower | Statement: [npower Championship, sponsor, npower]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: npower Context triple: [npower Championship, sponsor, npower]
-
A.
npower
chosen
npower is a UK-based energy company that has served as a major commercial sponsor of professional sports, including English football.
-
B.
POWER1
POWER1 is IBM’s first-generation 32-bit RISC microprocessor architecture used in early RS/6000 workstations and servers.
-
C.
POWER2
POWER2 is a second-generation IBM RISC microprocessor architecture designed to deliver high-performance computing, particularly for scientific and technical workloads.
-
D.
PWR
PWR is a global interfaith organization that convenes leaders and followers of diverse religious and spiritual traditions to promote dialogue, understanding, and cooperation for peace and justice.
-
E.
POWER4
POWER4 is a 64-bit microprocessor developed by IBM that introduced a dual-core design and high-performance server capabilities in the early 2000s.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96ff3a7208190b93f6292ed5efc07 |
completed | April 10, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a54838888190804202e45a55de48 |
completed | May 3, 2026, 1:30 a.m. |
Created at: April 9, 2026, 5:35 p.m.