Triple
T13806697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NR SR |
E331778
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | NR SR |
E331778
|
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 SR | Statement: [NR SR, abbreviation, NR SR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NR SR Context triple: [NR SR, abbreviation, NR SR]
-
A.
NR SR
chosen
NR SR is the commonly used abbreviation for the National Council of the Slovak Republic, the unicameral legislative body and primary lawmaking institution of Slovakia.
-
B.
NR
NR is the standard abbreviation for National Rail, the collective network of passenger railway services in Great Britain.
-
C.
NR
NR is the two-letter ISO 3166-1 alpha-2 country code assigned to the Republic of Nauru.
-
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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026d98108190acf366a36d97bf92 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b08db39c8190a76637b36b77d643 |
completed | May 3, 2026, 8:31 p.m. |
Created at: April 9, 2026, 10:12 p.m.