Triple
T21319083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronneby Airport |
E525560
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | RNB |
—
|
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: RNB | Statement: [Ronneby Airport, hasCode, RNB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RNB Context triple: [Ronneby Airport, hasCode, RNB]
-
A.
RNB
chosen
RNB is the IATA airport code for Ronneby Airport, a regional airport in southern Sweden serving the Blekinge area.
-
B.
RB
RB is the abbreviation for CERN’s Research Board, the committee responsible for overseeing and approving the laboratory’s scientific research program.
-
C.
RB
RB is the standard abbreviation for *Revue Biblique*, a scholarly journal specializing in biblical studies and related research.
-
D.
RB
RB is a common train service designation in German-speaking countries referring to RegionalBahn, which operates short- to medium-distance regional passenger rail services with frequent stops.
-
E.
RBN
RBN is the station code for Robina railway station on Queensland Rail's Gold Coast line in Robina, Queensland, Australia.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ecf12248190bb4172ad7416775e |
completed | April 21, 2026, 1:42 p.m. |
Created at: April 16, 2026, 4:38 p.m.