Triple

T31335525
Position Surface form Disambiguated ID Type / Status
Subject Comunera Province E799163 entity
Predicate colonialPowerInPeriod P130899 FINISHED
Object Spanish Empire 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: Spanish Empire | Statement: [Comunera Province, colonialPowerInPeriod, Spanish Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: colonialPowerInPeriod
Context triple: [Comunera Province, colonialPowerInPeriod, Spanish Empire]
  • A. colonialPowerInHistory chosen
    Indicates that one entity historically exercised colonial control, dominance, or governance over another entity.
  • B. colonialPowerBefore
    Indicates that one entity served as the colonial ruling power over another entity during an earlier, preceding time period.
  • C. colonialPowerAfter
    Indicates that one entity became the colonial ruler of another entity after a specified time or event, succeeding a previous colonial authority.
  • D. colonialPowerInvolved
    Indicates that a colonial power is involved in, influences, or exerts control over the referenced situation, event, or relationship.
  • E. periodOfColonialRule
    Indicates the time span during which one political power exercised colonial control over another territory or people.
  • 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_69f224e3f6ac8190a13488516abca7c9 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6b49436b0819094e21603054d05d4 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b3a7bdb481908d16a32f49e38c2c completed May 3, 2026, 2:32 a.m.
Created at: April 29, 2026, 9:16 p.m.