Triple

T577336
Position Surface form Disambiguated ID Type / Status
Subject Health Connect E13783 entity
Predicate targetDeveloper P13609 FINISHED
Object health app developers 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: health app developers | Statement: [Health Connect, targetDeveloper, health app developers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: targetDeveloper
Context triple: [Health Connect, targetDeveloper, health app developers]
  • A. developedWith
    Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
  • B. coDeveloperOf
    Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
  • C. developedAs
    Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
  • D. developedUnder
    Indicates that something was created, produced, or brought into existence while being subject to the authority, guidance, or conditions imposed by a particular person, organization, regime, or framework.
  • E. developmentRole chosen
    Indicates that an entity participates in the creation, design, or production of another entity in a specific developmental capacity 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_69a4933fa4d88190a7949cc83c08c5c1 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49b68cc808190b1ba45bdad78443d completed March 1, 2026, 8:02 p.m.
PD Predicate disambiguation batch_69a494c692288190b88f30299516b5ba completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:33 p.m.