Triple
T7927082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adamski |
E184091
|
entity |
| Predicate | notableSingle |
P3283
|
FINISHED |
| Object | N-R-G |
E700291
|
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: N-R-G | Statement: [Adamski, notableSingle, N-R-G]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N-R-G Context triple: [Adamski, notableSingle, N-R-G]
-
A.
N-R-G
chosen
"N-R-G" is a 1990 rave/acid house track by British producer Adamski that became one of his early breakthrough club hits.
-
B.
RNR
RNR is the abbreviation for the Royal Naval Reserve, the volunteer reserve force of the United Kingdom’s Royal Navy.
-
C.
NSRGY
NSRGY is the American over-the-counter (OTC) ADR representing shares of Nestlé S.A., the multinational Swiss food and beverage company.
-
D.
NR
NR is the U.S. Navy’s Office of Naval Reactors, the organization responsible for the design, operation, and safety of naval nuclear propulsion systems.
-
E.
NR
NR is the radio access technology standard defined by 3GPP for fifth-generation (5G) mobile networks, enabling high-speed, low-latency wireless communication.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aafdb5c8190b7f2ce5349305f78 |
completed | March 31, 2026, 3:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe00951748190b6036cb359f2a6e3 |
completed | March 31, 2026, 2:54 p.m. |
Created at: March 30, 2026, 5:07 p.m.