Triple
T2992580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Navy |
E80990
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | RCN |
E80990
|
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: RCN | Statement: [Royal Canadian Navy, abbreviation, RCN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RCN Context triple: [Royal Canadian Navy, abbreviation, RCN]
-
A.
RCN
RCN is the commonly used abbreviation for the Research Council of Norway, the national body responsible for funding and promoting research and innovation in Norway.
-
B.
RCN
chosen
RCN is the abbreviation for the Royal Canadian Navy, the maritime warfare branch of Canada’s armed forces.
-
C.
CRN
CRN is the ICAO airline designator assigned to the Cuban regional carrier AeroCaribbean.
-
D.
RCM
RCM is a Canadian Earth observation satellite constellation that uses radar imaging to monitor environmental changes, maritime activity, and national security.
-
E.
RKC
RKC is the commonly used abbreviation for the Revised Kyoto Convention, an international agreement that standardizes and simplifies customs procedures worldwide.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99e12c5c8190af7cc20e4c48bf45 |
completed | March 8, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b109061684819086777d3b871c94f8 |
completed | March 11, 2026, 6:17 a.m. |
Created at: March 8, 2026, 2:59 p.m.