Triple
T36514437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 3 |
E899997
|
entity |
| Predicate | designerBureau |
P25389
|
FINISHED |
| Object | Sergei Korolev Design Bureau |
—
|
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: Sergei Korolev Design Bureau | Statement: [Soyuz 3, designerBureau, Sergei Korolev Design Bureau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designerBureau Context triple: [Soyuz 3, designerBureau, Sergei Korolev Design Bureau]
-
A.
designBureau
chosen
Indicates that an entity functions as a design bureau responsible for planning, developing, or engineering designs for another entity or project.
-
B.
designBureauNamedAfter
Indicates that a design bureau is named in honor of or after a particular person, organization, or entity.
-
C.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
D.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
E.
designerEmployer
Indicates that one entity is the employer or employing organization of a designer in relation to a design activity or role.
- F. None of above.
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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: May 3, 2026, 4:10 p.m.