Triple

T34989447
Position Surface form Disambiguated ID Type / Status
Subject Vault City E1009339 entity
Predicate citizenshipPolicy P84970 FINISHED
Object strict citizenship laws 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: strict citizenship laws | Statement: [Vault City, citizenshipPolicy, strict citizenship laws]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: citizenshipPolicy
Context triple: [Vault City, citizenshipPolicy, strict citizenship laws]
  • A. leaderCitizenship
    Indicates that a leader holds citizenship in, or is a national of, a particular country or political entity.
  • B. citizenshipContext
    Indicates the legal or social circumstances under which an entity holds or is granted citizenship in a particular state or jurisdiction.
  • C. nationalityPolicy chosen
    Indicates the policy or rules a state or organization applies regarding the national affiliation or citizenship status of individuals.
  • D. citizenshipIssue
    Indicates that there is a problem, dispute, or complication concerning an entity’s citizenship status or rights.
  • E. citizenshipCommon
    Indicates that the related entities share the same citizenship or nationality.
  • 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_69f76dca50dc8190b71f39defe186be8 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78ce78b508190955848e133398dc8 completed May 3, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69f78b8f4cc08190b49fccd798cb25d7 completed May 3, 2026, 5:53 p.m.
Created at: May 3, 2026, 4:01 p.m.