Triple

T28478165
Position Surface form Disambiguated ID Type / Status
Subject Boland Amendment E720616 entity
Predicate legalContextFor P2132 FINISHED
Object Iran–Contra affair NE NERFINISHED

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: Iran–Contra affair | Statement: [Boland Amendment, legalContextFor, Iran–Contra affair]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalContextFor
Context triple: [Boland Amendment, legalContextFor, Iran–Contra affair]
  • A. legalContext chosen
    Indicates that the relationship or action occurs within, is shaped by, or is relevant to a specific legal framework, proceeding, or set of legal norms.
  • B. legalScope
    Indicates the range, boundaries, or extent of authority, applicability, or effect that something has under a particular legal framework or rule.
  • C. legalBackground
    Indicates that an entity has education, training, or experience related to law or the legal profession.
  • D. legalContent
    Indicates that the associated material complies with applicable laws and regulations and is permitted for use, distribution, or display.
  • E. legalTarget
    Indicates that an action, decision, or rule is directed toward an entity in a manner that is permitted or recognized as valid under the governing legal or rule system.
  • 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_69f01a5983f48190b7c1b8857245a4f7 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69fd2cf39b0c8190811b8a6fa9410560 completed May 8, 2026, 12:23 a.m.
PD Predicate disambiguation batch_69fd2ad8dd988190a9899701ba00d917 completed May 8, 2026, 12:14 a.m.
Created at: April 28, 2026, 2:53 a.m.