Triple
T16807654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blok DM |
E408519
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Blok DM-3 |
E408519
|
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: Blok DM-3 | Statement: [Blok DM, hasVariant, Blok DM-3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blok DM-3 Context triple: [Blok DM, hasVariant, Blok DM-3]
-
A.
Blok DM
chosen
Blok DM is a Russian upper stage used primarily on Proton and Zenit launch vehicles to deliver payloads into high-energy orbits such as geostationary transfer and lunar trajectories.
-
B.
Blok
Blok is a Russian surname most famously borne by the Symbolist poet Alexander Blok.
-
C.
Blok-L
Blok-L is a Soviet-era rocket upper stage used primarily to place payloads into highly elliptical orbits, notably for Molniya communications satellites.
-
D.
S-blokka
S-blokka is a government office building in Oslo, Norway, that forms part of the Norwegian Government Quarter complex.
-
E.
Blok M
Blok M is a major commercial and entertainment district in Jakarta known for its bustling shopping centers, street markets, and vibrant nightlife.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cde590819080dc474292b023ee |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb0dce448190b20ca3d60d9fc475 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:22 a.m.