Triple

T10342029
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam Treaty E243147 entity
Predicate strengthenedPolicyArea P93789 FINISHED
Object common foreign and security 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: common foreign and security policy | Statement: [Amsterdam Treaty, strengthenedPolicyArea, common foreign and security policy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strengthenedPolicyArea
Context triple: [Amsterdam Treaty, strengthenedPolicyArea, common foreign and security policy]
  • A. emphasizesPolicyArea
    Indicates that one entity gives particular importance or priority to a specific policy area in its actions, statements, or focus.
  • B. commonPolicyArea
    Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
  • C. isPartOfPolicyArea
    Indicates that one policy, topic, or issue belongs to, falls under, or is categorized within a broader policy area or domain.
  • D. implementsPolicyArea
    Indicates that an entity carries out, enforces, or operationalizes a specific policy area in practice.
  • E. supportsPolicyArea
    Indicates that one entity endorses, advocates for, or is in favor of a particular policy area or domain of public policy.
  • 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_69d381af787481908bc401325c760a88 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e91fdb2081909866c6ecf417d75a completed April 7, 2026, 11:23 a.m.
PD Predicate disambiguation batch_69d4df9dc3208190bf1bd106f44f6202 completed April 7, 2026, 10:42 a.m.
PDg Predicate description generation batch_69d4e91ce2008190af252c140370b7f2 completed April 7, 2026, 11:23 a.m.
Created at: April 6, 2026, 11:55 a.m.