Triple
T37648916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavochkin La-15 (late prototypes / trials) |
E937114
|
entity |
| Predicate | designBureauHead |
P179196
|
FINISHED |
| Object | Semyon Lavochkin |
—
|
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: Semyon Lavochkin | Statement: [Lavochkin La-15 (late prototypes / trials), designBureauHead, Semyon Lavochkin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designBureauHead Context triple: [Lavochkin La-15 (late prototypes / trials), designBureauHead, Semyon Lavochkin]
-
A.
designBureau
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.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
D.
designedByFirmHeadedBy
chosen
Indicates that something was designed by a firm whose leader or head is a specified person.
-
E.
designedHead
Indicates that one entity is the primary designer or creator responsible for the conception or design of another entity.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:18 p.m.