Triple
T21889102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Norwegian Navy |
E540489
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | RNoN |
—
|
NE NERFINISHED |
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: RNoN | Statement: [Royal Norwegian Navy, abbreviation, RNoN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RNoN Context triple: [Royal Norwegian Navy, abbreviation, RNoN]
-
A.
RNoN
chosen
RNoN is the abbreviation for the Royal Norwegian Navy, the maritime branch of Norway's armed forces.
-
B.
RNoM
RNoM is the post-nominal abbreviation used by recipients of the Royal Norwegian Order of Merit, a Norwegian order awarded for outstanding service in the interests of Norway.
-
C.
RNO
RNO is the three-letter IATA airport code for Reno–Tahoe International Airport, the primary commercial airport serving Reno, Nevada and the surrounding Lake Tahoe region.
-
D.
RNO
RNO is the stock ticker symbol for Renault, the French multinational automobile manufacturer listed on the Euronext Paris exchange.
-
E.
RNO
RNO is the standard abbreviation used for the Reno Bighorns basketball team.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ef2b648190bbd78f6b3958d2ee |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 16, 2026, 7:05 p.m.