Triple
T20491584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RB-50 |
E502757
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | RB-50G |
—
|
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: RB-50G | Statement: [RB-50, hasVariant, RB-50G]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RB-50G Context triple: [RB-50, hasVariant, RB-50G]
-
A.
RB-50
chosen
The RB-50 was a reconnaissance and weather reconnaissance variant of the Boeing B-50 Superfortress used by the United States Air Force during the early Cold War.
-
B.
RB-47
The RB-47 was a reconnaissance version of the Boeing B-47 Stratojet, used primarily during the Cold War for strategic photographic and electronic intelligence missions.
-
C.
R-5
R-5 is a motorway designated with the abbreviation R-5, typically referring to a regional or ring road route in a national highway network.
-
D.
R-5
The R-5 is an early Sikorsky military helicopter developed during World War II, known for advancing rotary-wing design and serving in roles such as rescue and liaison.
-
E.
RJ‑21
RJ‑21 is the motor vehicle registration code assigned to the Nagaur district in the Indian state of Rajasthan.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cba5b708190bef437acf6321b81 |
completed | April 20, 2026, 9:38 p.m. |
Created at: April 16, 2026, 11:35 a.m.