Triple

T3406191
Position Surface form Disambiguated ID Type / Status
Subject Aden Protectorate E71776 entity
Predicate hadStatusChange P35872 FINISHED
Object divided into Eastern and Western Aden Protectorates in 1937 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: divided into Eastern and Western Aden Protectorates in 1937 | Statement: [Aden Protectorate, hadStatusChange, divided into Eastern and Western Aden Protectorates in 1937]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadStatusChange
Context triple: [Aden Protectorate, hadStatusChange, divided into Eastern and Western Aden Protectorates in 1937]
  • A. statusChange chosen
    Indicates a transition in an entity’s state or condition from one status to another over time.
  • B. hadStateFrom
    Indicates that an entity possessed or was in a particular state starting from a specified point in time.
  • C. hadSpecialStatusIn
    Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
  • D. hasHad
    Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
  • E. hadEvent
    Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
  • 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_69ad85aac4808190a092c9cc8911f584 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb8ec68c88190913df5f6cafad9e9 completed March 8, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69adadfa73ac8190a163f93e88d217f8 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:15 p.m.