Triple
T6799044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic Council |
E156133
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | NR |
E156133
|
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: NR | Statement: [Nordic Council, hasAbbreviation, NR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NR Context triple: [Nordic Council, hasAbbreviation, NR]
-
A.
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.
-
B.
NR
NR is the radio access technology standard defined by 3GPP for fifth-generation (5G) mobile networks, enabling high-speed, low-latency wireless communication.
-
C.
NR
NR is the standard abbreviation for National Rail, the collective network of passenger railway services in Great Britain.
-
D.
NR
chosen
NR is the commonly used abbreviation for the Nordic Council, a regional inter-parliamentary body for cooperation among the Nordic countries.
-
E.
NR
NR is the two-letter ISO 3166-1 alpha-2 country code assigned to the Republic of Nauru.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2cb6b2881909b30bb8020a9d3bf |
completed | March 27, 2026, 6:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71a9826648190b4f59c1a8efc4b9c |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:15 p.m.