Triple

T22445610
Position Surface form Disambiguated ID Type / Status
Subject Fuchsia E554855 entity
Predicate usesCapabilityModel P148227 FINISHED
Object capability-based security 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: capability-based security | Statement: [Fuchsia, usesCapabilityModel, capability-based security]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCapabilityModel
Context triple: [Fuchsia, usesCapabilityModel, capability-based security]
  • A. usedCapability
    Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
  • B. requiresCapability
    Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
  • C. definesCapability
    Indicates that one entity specifies or establishes the abilities, functions, or capacities that another entity can possess or perform.
  • D. isPartOfCapability
    Indicates that one capability is a component or sub-function within a broader, composite capability.
  • E. demonstratedCapability
    Indicates that an entity has shown, through evidence or performance, the ability to carry out a specific action or function.
  • 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_69e11e5113208190ab58c6b595f9d1d0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15b46e8ac8190bfa8c611ffcba822 completed April 29, 2026, 1:13 a.m.
PD Predicate disambiguation batch_69e898ad961c819098fd1e46129bddcc completed April 22, 2026, 9:45 a.m.
PDg Predicate description generation batch_69e8aa39e3388190b659d59948ebf3e6 completed April 22, 2026, 11 a.m.
Created at: April 16, 2026, 8:47 p.m.