Triple

T3185877
Position Surface form Disambiguated ID Type / Status
Subject Treaty of San Ildefonso (1796) E66696 entity
Predicate obligationsOfSpain P46503 FINISHED
Object to support France with naval forces 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: to support France with naval forces | Statement: [Treaty of San Ildefonso (1796), obligationsOfSpain, to support France with naval forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: obligationsOfSpain
Context triple: [Treaty of San Ildefonso (1796), obligationsOfSpain, to support France with naval forces]
  • A. effectOnSpain
    Indicates a relationship where one entity produces an influence, change, or consequence specifically affecting Spain.
  • B. legalStatusWithinCastile
    Indicates the legal standing or rights an entity holds under the laws and jurisdiction specific to Castile.
  • C. commanderForSpain
    Indicates that a person serves or has served as a military commander on behalf of Spain.
  • D. strategicObjectiveSpain
    Indicates that an entity has a strategic objective specifically related to Spain.
  • E. allyInWarOfTheSpanishSuccession
    Indicates that the subject entity was an ally of the object entity during the War of the Spanish Succession.
  • 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_69ad8587c1bc8190a2595f2c22ee1001 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada6c1341081909793f8d05fddfd5e completed March 8, 2026, 4:41 p.m.
PD Predicate disambiguation batch_69ad9e04290481909092ddfbe6fdaabc completed March 8, 2026, 4:04 p.m.
PDg Predicate description generation batch_69ada148e9108190b363dd0f1a94ac8e completed March 8, 2026, 4:18 p.m.
Created at: March 8, 2026, 3:06 p.m.