Triple

T22489416
Position Surface form Disambiguated ID Type / Status
Subject Adobe Flex E555973 entity
Predicate supportsDataBinding P148413 FINISHED
Object two-way data binding 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: two-way data binding | Statement: [Adobe Flex, supportsDataBinding, two-way data binding]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsDataBinding
Context triple: [Adobe Flex, supportsDataBinding, two-way data binding]
  • A. supportsContextBinding
    Indicates that one entity enables or maintains the association of another entity with a specific execution or usage context so that related operations remain correctly bound to that context.
  • B. supportsDataFrom
    Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
  • C. supportsLanguageBindingSystem
    Indicates that one entity provides mechanisms or infrastructure that enable another entity to create, use, or integrate language bindings for a system or platform.
  • D. supportsDatabaseConnectivity
    Indicates that an entity provides the capability to establish and maintain connections to a database system.
  • E. supportsAggregation
    Indicates that one entity enables or allows another entity to be combined, grouped, or summarized with others through an aggregation operation.
  • 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_69e11e53897c819088863779f8c50bb0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15c3f3b4c819092bfe6495c61db46 completed April 29, 2026, 1:17 a.m.
PD Predicate disambiguation batch_69e898b6eee08190ba673a0ee329e671 completed April 22, 2026, 9:45 a.m.
PDg Predicate description generation batch_69e8aa3b4c288190951cca06d42bea51 completed April 22, 2026, 11 a.m.
Created at: April 16, 2026, 8:49 p.m.