Triple
T9082651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok-L |
E217670
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | 8K72 |
E207526
|
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: 8K72 | Statement: [Vostok-L, alsoKnownAs, 8K72]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 8K72 Context triple: [Vostok-L, alsoKnownAs, 8K72]
-
A.
8K72K
chosen
8K72K is the GRAU index designation for the Vostok-K, a Soviet launch vehicle used in the early 1960s to orbit crewed Vostok spacecraft and various satellites.
-
B.
K7
K7 is the registration number of the Bluebird K7, the famous mid-20th-century hydroplane in which Donald Campbell set multiple world water speed records.
-
C.
J80
J80 is the internal chassis code used by Toyota for the 80-series Land Cruiser platform that underpins the first-generation Lexus LX luxury SUV.
-
D.
J7
J7 is a numbered junction on the M60 motorway in Greater Manchester, England, serving as an access point between the motorway and the surrounding local road network.
-
E.
KR-48
KR-48 is the ISO 3166-2 subdivision code assigned to South Korea’s South Gyeongsang Province, which includes the city of Miryang.
- 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_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc960a2760819084aab611eb1c43a9 |
completed | April 1, 2026, 3:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffe30093481908b3ec394cf585642 |
completed | April 3, 2026, 5:51 p.m. |
Created at: March 30, 2026, 7:13 p.m.