Triple

T12037006
Position Surface form Disambiguated ID Type / Status
Subject CITES Appendix I E286564 entity
Predicate relationshipToConventionText P21040 FINISHED
Object defined in Articles II and III of CITES 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: defined in Articles II and III of CITES | Statement: [CITES Appendix I, relationshipToConventionText, defined in Articles II and III of CITES]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relationshipToConventionText
Context triple: [CITES Appendix I, relationshipToConventionText, defined in Articles II and III of CITES]
  • A. relationshipToConventions chosen
    Indicates how something is associated or connected to a set of conventions, such as rules, standards, or agreed practices.
  • B. relationshipToEvent
    Indicates the specific way an entity is connected or related to a particular event.
  • C. associatedConvention
    Indicates a relationship where something is linked or connected to a particular convention (such as an event, standard, or formal gathering).
  • D. relationshipType
    Indicates the specific kind of relationship that exists between two or more entities.
  • E. relationshipToState
    Indicates a relationship or connection that an entity has with a particular state or governmental body.
  • 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_69d6ab4669e48190b59246358b0383ab completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9100b4ca8819084845ca4c13e34ce completed April 10, 2026, 2:58 p.m.
PD Predicate disambiguation batch_69d902bac9e08190aa1a99c835f29542 completed April 10, 2026, 2:01 p.m.
Created at: April 8, 2026, 9:47 p.m.