Triple
T7282536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ready Reserve Force |
E163785
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | RRF |
E163785
|
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: RRF | Statement: [Ready Reserve Force, acronym, RRF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RRF Context triple: [Ready Reserve Force, acronym, RRF]
-
A.
RRF
chosen
RRF is the acronym for the United States Ready Reserve Force, a fleet of government-owned cargo ships maintained for rapid activation in military and humanitarian sealift operations.
-
B.
RR
RR is the standard abbreviation for the ITU’s international Radio Regulations, which govern the global use of the radio-frequency spectrum and satellite orbits.
-
C.
RIF
RIF (Rule Interchange Format) is a W3C standard designed to enable the exchange and interoperability of rules across different Semantic Web systems and rule engines.
-
D.
.rf
.rf is the Cyrillic country-code top-level domain representing the Russian Federation on the internet.
-
E.
FFR
FFR is the commonly used abbreviation for the French Rugby Federation, the governing body for rugby union in France.
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb4d3e3c8190a05cb5af5f52bd75 |
completed | March 27, 2026, 8:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7db3ae6a08190820c7096cbfea521 |
completed | March 28, 2026, 1:44 p.m. |
Created at: March 27, 2026, 2:59 p.m.