Triple

T37472014
Position Surface form Disambiguated ID Type / Status
Subject Drust E931175 entity
Predicate usesConstructs P35482 FINISHED
Object Drust constructs 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: Drust constructs | Statement: [Drust, usesConstructs, Drust constructs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesConstructs
Context triple: [Drust, usesConstructs, Drust constructs]
  • A. constructs
    Indicates that an agent builds, creates, or assembles something, typically resulting in a new or more complex entity or structure.
  • B. coreConstruct
    Indicates a fundamental building or organizing relationship where one entity serves as the essential basis or primary component from which another entity is formed or structured.
  • C. canBeConstructedWith
    Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
  • D. isConstructive
    Indicates that an action, behavior, or contribution has a positive, helpful, or improvement-oriented effect on a situation or outcome.
  • E. usedStructure chosen
    Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
  • 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_69f76ec2af148190897d101070d7f415 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fe744faca881908e11e90e0a35653f completed May 8, 2026, 11:39 p.m.
PD Predicate disambiguation batch_69fe734cbf7081909a552c5cf3b5ea59 completed May 8, 2026, 11:35 p.m.
Created at: May 3, 2026, 4:17 p.m.