Triple
T5535794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mechta |
E145157
|
entity |
| Predicate | spaceAgency |
P10670
|
FINISHED |
| Object | OKB-1 |
E61666
|
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: OKB-1 | Statement: [Mechta, spaceAgency, OKB-1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OKB-1 Context triple: [Mechta, spaceAgency, OKB-1]
-
A.
OKB-1
chosen
OKB-1 was the Soviet Union’s leading spacecraft and rocket design bureau that developed early ballistic missiles and the first spacecraft under chief designer Sergei Korolev.
-
B.
OKB Sukhoi
OKB Sukhoi is a major Russian aerospace design bureau renowned for developing a wide range of military aircraft, including advanced fighter jets and bombers.
-
C.
OKS
OKS is the abbreviation commonly used for the National Olympic Committee of Serbia, the body responsible for organizing the country’s participation in the Olympic Games.
-
D.
OKM
OKM was the abbreviation for the Oberkommando der Marine, the supreme command authority of Nazi Germany’s Kriegsmarine (navy) during World War II.
-
E.
OKA
OKA is the IATA airport code for Naha Airport, the main air gateway to Okinawa, Japan.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01faed1d08190b6a57faedaf1b56a |
completed | March 22, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c02814359c8190b868811f22aa568c |
completed | March 22, 2026, 5:34 p.m. |
Created at: March 22, 2026, 3:34 p.m.