Triple
T13885511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhein-Neckar-Verkehr |
E333831
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | rnv |
E1067967
|
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: rnv | Statement: [Rhein-Neckar-Verkehr, abbreviation, rnv]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: rnv Context triple: [Rhein-Neckar-Verkehr, abbreviation, rnv]
-
A.
rnv
chosen
rnv is the public transport brand of Rhein-Neckar-Verkehr, operating buses and trams in Germany’s Rhine-Neckar metropolitan region.
-
B.
RNR
RNR is the abbreviation for the Royal Naval Reserve, the volunteer reserve force of the United Kingdom’s Royal Navy.
-
C.
RNVR
RNVR is the abbreviation for the Royal Naval Volunteer Reserve, a former volunteer reserve force of the British Royal Navy composed of civilian sailors and officers.
-
D.
RVD
RVD is the ring name of Rob Van Dam, a high-flying, innovative professional wrestler best known for his time in ECW and WWE.
-
E.
RUVNN
RUVNN is the international port code assigned to the seaport of Vanino in Russia.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7ce6facd48190b310099fbd52bdf0 |
completed | May 3, 2026, 10:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.