Triple

T35945417
Position Surface form Disambiguated ID Type / Status
Subject Capparales E1039574 entity
Predicate notUsedInClassificationSystem P116723 FINISHED
Object APG II system 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: APG II system | Statement: [Capparales, notUsedInClassificationSystem, APG II system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notUsedInClassificationSystem
Context triple: [Capparales, notUsedInClassificationSystem, APG II system]
  • A. notClassifiedAs
    Indicates that an entity is explicitly not assigned to, or excluded from, a particular class or category.
  • B. notUsedInDomain chosen
    Indicates that a given element or resource is not utilized, referenced, or applicable within a specified domain or context.
  • C. notUsedAt
    Indicates that a particular entity is not utilized, applied, or active at a specified location, time, or context.
  • D. notUsedOver
    Indicates that one entity has not been used, applied, or utilized for a duration exceeding a specified time period relative to another entity or reference point.
  • E. notAutomaticallyUsedBy
    Indicates that something is not used by another entity in an automatic or default manner and instead requires explicit action or configuration to be used.
  • 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_69f76e24bbd0819096b837d35371639a completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7ac23d1388190bdf9628b294943bd completed May 3, 2026, 8:12 p.m.
PD Predicate disambiguation batch_69f7ab734d848190a84f9b8c3a952b75 completed May 3, 2026, 8:09 p.m.
Created at: May 3, 2026, 4:07 p.m.