Triple

T17553725
Position Surface form Disambiguated ID Type / Status
Subject Andean Community institutions E427535 entity
Predicate coordinatesPolicyArea P54254 FINISHED
Object trade policy 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: trade policy | Statement: [Andean Community institutions, coordinatesPolicyArea, trade policy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coordinatesPolicyArea
Context triple: [Andean Community institutions, coordinatesPolicyArea, trade policy]
  • A. coversPolicyArea
    Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
  • B. hasPolicyArea
    Indicates that an entity (such as a policy, program, or initiative) is associated with or pertains to a specific policy area or domain.
  • C. coordinatesGovernmentPolicyIn chosen
    Indicates that an entity organizes, aligns, or manages government policy activities within a specified location or jurisdiction.
  • D. commonPolicyArea
    Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
  • E. isPartOfPolicyArea
    Indicates that one policy, topic, or issue belongs to, falls under, or is categorized within a broader policy area or domain.
  • 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_69d889df6dc081908f67dbadc03c07ee completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e45620983c81909e71f938ce934efa completed April 19, 2026, 4:12 a.m.
PD Predicate disambiguation batch_69e3b4fb39948190a82a597c5bac5c57 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:50 a.m.