Triple
T13044167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redcaps |
E327273
|
entity |
| Predicate | usesAbbreviation |
P43
|
FINISHED |
| Object | RMP |
E327272
|
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: RMP | Statement: [Redcaps, usesAbbreviation, RMP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RMP Context triple: [Redcaps, usesAbbreviation, RMP]
-
A.
RMP
chosen
RMP is the abbreviation for the Royal Military Police, the branch of the British Army responsible for policing service personnel and maintaining military law and order.
-
B.
RPM
RPM is a widely used package management system originally developed for Linux distributions to build, install, and manage software packages.
-
C.
RM
RM is a South Korean rapper, songwriter, and leader of the globally renowned K-pop group BTS.
-
D.
RM
RM is the currency symbol that was used to denote the German Reichsmark, the former official currency of Germany from 1924 to 1948.
-
E.
RM
RM is a UK postcode area in east London and parts of Essex, covering districts such as Romford and surrounding suburbs.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98050157c8190bb8c640b759ac2b7 |
completed | April 10, 2026, 10:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5fdd04c8190a86dbba1b81c8e6b |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 8:56 p.m.