Triple

T7388096
Position Surface form Disambiguated ID Type / Status
Subject HardCopy E170431 entity
Predicate reconfigurability P76303 FINISHED
Object non-reconfigurable in the field 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: non-reconfigurable in the field | Statement: [HardCopy, reconfigurability, non-reconfigurable in the field]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reconfigurability
Context triple: [HardCopy, reconfigurability, non-reconfigurable in the field]
  • A. configuration
    Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
  • B. reusability
    Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
  • C. reversibility
    Indicates that a process, action, or transformation can be undone or reversed to restore the original state or conditions.
  • D. refit
    Indicates that an existing object or structure is being modified, repaired, or equipped with new parts or features to restore or improve its function.
  • E. reversible
    Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
  • F. None of above. chosen

Provenance (4 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_69c68a5e2c9081909e713ce866e0060a completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f1f3f5f48190aabe69ba79cbcb93 completed March 27, 2026, 9:09 p.m.
PD Predicate disambiguation batch_69c6f0309cc88190b55d278969400294 completed March 27, 2026, 9:01 p.m.
PDg Predicate description generation batch_69c6f0be2b1c8190bea06100a7caef2b completed March 27, 2026, 9:03 p.m.
Created at: March 27, 2026, 3:09 p.m.