Triple
T18039253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angara |
E431596
|
entity |
| Predicate | usesUpperStage |
P56081
|
FINISHED |
| Object | Briz-M |
—
|
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: Briz-M | Statement: [Angara, usesUpperStage, Briz-M]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Briz-M Context triple: [Angara, usesUpperStage, Briz-M]
-
A.
Briz-M
chosen
Briz-M is a Russian expendable upper stage used to place payloads into high orbits, most commonly in combination with Proton launch vehicles.
-
B.
Brenz
The Brenz is a river in southern Germany that flows through Baden-Württemberg and Bavaria before joining the Danube.
-
C.
BZR
BZR is the IATA airport code for Béziers Cap d’Agde Airport, a regional airport in southern France serving the Béziers and Cap d’Agde area.
-
D.
Blisk
Blisk is a fictional setting or universe in which the character or concept known as Blink appears or is utilized.
-
E.
Blisk
Blisk is a developer-focused web browser designed for building and testing websites, featuring tools like synchronized device emulation and automatic refresh.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be3cbe8c8190ba216eeebfc3cbec |
completed | April 19, 2026, 11:36 a.m. |
Created at: April 10, 2026, 10:25 a.m.