Triple

T27412171
Position Surface form Disambiguated ID Type / Status
Subject Alexander Morozov E692181 entity
Predicate designedComponent P57584 FINISHED
Object hull layout of the T-34 LITERAL 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: hull layout of the T-34 | Statement: [Alexander Morozov, designedComponent, hull layout of the T-34]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedComponent
Context triple: [Alexander Morozov, designedComponent, hull layout of the T-34]
  • A. designedObject
    Indicates that one entity is the creator or designer of another entity as its intended product or outcome.
  • B. designedWith
    Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
  • C. designedFeature chosen
    Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
  • D. developsComponentFor
    Indicates that one entity creates or builds a component intended to be used by or within another entity.
  • E. designedAsPartOfSystemBy
    Indicates that an entity was intentionally created as a component or module within a larger system by a specific designer or designing agent.
  • 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_69ef5205fc808190ad3efc5525b8e6d6 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: April 27, 2026, 12:32 p.m.