Triple
T6326881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Netherlands Navy |
E141883
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | RNLN |
E141883
|
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: RNLN | Statement: [Royal Netherlands Navy, abbreviation, RNLN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RNLN Context triple: [Royal Netherlands Navy, abbreviation, RNLN]
-
A.
RNLN
chosen
RNLN is the abbreviation commonly used for the Royal Netherlands Navy, the maritime branch of the Dutch armed forces.
-
B.
LN1
LN1 is the first French high-speed rail line (LGV Sud-Est), connecting Paris to Lyon and pioneering the TGV network.
-
C.
NNL
NNL is the commonly used abbreviation for the Negro National League, a pioneering professional baseball league that was a cornerstone of Negro league baseball in the early 20th century.
-
D.
RNLA
RNLA is the abbreviation for the Royal Netherlands Army, the land forces branch of the Dutch Armed Forces.
-
E.
N line
The N line is a service of the New York City Subway system that runs through Manhattan, Brooklyn, and Queens, connecting key neighborhoods and major transit hubs.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e833a0819096000b47e776949d |
completed | March 22, 2026, 9:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c60410223081908c1cf3663d4b14c0 |
completed | March 27, 2026, 4:14 a.m. |
Created at: March 22, 2026, 4:29 p.m.