Triple

T8771118
Position Surface form Disambiguated ID Type / Status
Subject 71-619 E208462 entity
Predicate hasCouplingCapability P14647 FINISHED
Object multiple-unit operation possible 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: multiple-unit operation possible | Statement: [71-619, hasCouplingCapability, multiple-unit operation possible]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCouplingCapability
Context triple: [71-619, hasCouplingCapability, multiple-unit operation possible]
  • A. couplingCapability chosen
    Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
  • B. hasCoupling
    Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
  • C. hasCouplingConstant
    Indicates that one entity is associated with a specific coupling constant value that quantifies the strength of an interaction or relationship.
  • D. hasCouplers
    Indicates that one entity is equipped with or possesses couplers that enable it to connect or link to another entity.
  • E. isCapableOf
    Indicates that an entity has the ability or capacity to perform a particular action or function.
  • 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_69ca835edb4481909b4aafb616dc5eb7 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5f2b08f881909f3d4fab2eda1d67 completed March 31, 2026, 11:56 p.m.
PD Predicate disambiguation batch_69cc5c1aff3881908be6a9cbc9f50461 completed March 31, 2026, 11:43 p.m.
Created at: March 30, 2026, 6:41 p.m.