Triple

T16798669
Position Surface form Disambiguated ID Type / Status
Subject NIH cooperative agreements (U-series awards) E408297 entity
Predicate hasFundingActivityCodePrefix P124673 FINISHED
Object U 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: U | Statement: [NIH cooperative agreements (U-series awards), hasFundingActivityCodePrefix, U]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFundingActivityCodePrefix
Context triple: [NIH cooperative agreements (U-series awards), hasFundingActivityCodePrefix, U]
  • A. hasOrganizationalCode
    Indicates that an entity is associated with a specific organizational code used to identify it within an organization’s structure or system.
  • B. hasPreCodeStatus
    Indicates that an entity held a specific code-related status or classification at some earlier point in time.
  • C. predecessorFundingModel
    Indicates that one funding model directly precedes and is replaced or updated by another funding model in a sequence or evolution of funding approaches.
  • D. permittedFundingFrom
    Indicates that providing financial resources from one entity to another is allowed under specified rules or conditions.
  • E. fundedBy
    Indicates that an entity receives financial support or resources from another entity.
  • 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2abc430819080c1303eded5f416 completed April 18, 2026, 4:34 p.m.
PD Predicate disambiguation batch_69e319d0fdb8819088425bd82431640f completed April 18, 2026, 5:42 a.m.
PDg Predicate description generation batch_69e326bac94481908c082117553320f8 completed April 18, 2026, 6:37 a.m.
Created at: April 10, 2026, 5:22 a.m.