Triple

T18916715
Position Surface form Disambiguated ID Type / Status
Subject Guerra del Asiento de Negros E462742 entity
Predicate causa P694 FINISHED
Object disputas comerciales entre Gran Bretaña y España 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: disputas comerciales entre Gran Bretaña y España | Statement: [Guerra del Asiento de Negros, causa, disputas comerciales entre Gran Bretaña y España]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: causa
Context triple: [Guerra del Asiento de Negros, causa, disputas comerciales entre Gran Bretaña y España]
  • A. causeOf chosen
    Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
  • B. causeStatus
    Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
  • C. causeInStory
    Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
  • D. end cause
    Indicates that one event or action brings about the termination or cessation of another event, state, or process.
  • E. causeOfClaim
    Indicates the underlying reason, event, or condition that gives rise to a particular claim.
  • 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_69d8dcfdbbb881909964fa5a75bd0b48 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c627724881909cf63c67d64321e8 completed April 20, 2026, 6:22 a.m.
PD Predicate disambiguation batch_69e4a2e9e6488190ba8df92c8058ed88 completed April 19, 2026, 9:39 a.m.
Created at: April 10, 2026, 11:58 a.m.