Triple
T17173695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Juno mission to Mir |
E416802
|
entity |
| Predicate | operator |
P179
|
FINISHED |
| Object | RKA |
E504398
|
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: RKA | Statement: [Project Juno mission to Mir, operator, RKA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RKA Context triple: [Project Juno mission to Mir, operator, RKA]
-
A.
RKA
chosen
RKA is the Russian Space Agency that managed Russia’s human spaceflight activities, including operations of the Mir space station.
-
B.
RJKA
RJKA is the ICAO airport code for Amami Airport, a regional airport serving Amami Ōshima in Kagoshima Prefecture, Japan.
-
C.
RKR
RKR is the vehicle registration code assigned to vehicles registered in the Rymanów area of Poland.
-
D.
RKC
RKC is the commonly used abbreviation for the Revised Kyoto Convention, an international agreement that standardizes and simplifies customs procedures worldwide.
-
E.
RKT
RKT is the IATA airport code for Ras Al Khaimah International Airport in the United Arab Emirates.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0b7c9c819082e503cb493d7e7b |
completed | April 18, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0148415c788190a4248b097f323d03 |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:37 a.m.