Triple

T6991022
Position Surface form Disambiguated ID Type / Status
Subject Common Monetary Area E162084 entity
Predicate policyCoordinationArea P54254 FINISHED
Object foreign exchange regulations 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: foreign exchange regulations | Statement: [Common Monetary Area, policyCoordinationArea, foreign exchange regulations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: policyCoordinationArea
Context triple: [Common Monetary Area, policyCoordinationArea, foreign exchange regulations]
  • A. policyAreaScope
    Indicates the specific policy domain or thematic area to which an action, decision, or measure is relevant or applies.
  • B. isPartOfPolicyArea
    Indicates that one policy, topic, or issue belongs to, falls under, or is categorized within a broader 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. governanceArea
    Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
  • 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_69c68856d7808190ab33ee914640281b completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dbc08758819083d36a1fc0463b27 completed March 27, 2026, 7:34 p.m.
PD Predicate disambiguation batch_69c6d7c4a18881908d267137daed828b completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:32 p.m.