Triple

T13857516
Position Surface form Disambiguated ID Type / Status
Subject EB-1 priority workers immigrant visa E333102 entity
Predicate selfPetitionAllowedForEB1A P111810 FINISHED
Object yes 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: yes | Statement: [EB-1 priority workers immigrant visa, selfPetitionAllowedForEB1A, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: selfPetitionAllowedForEB1A
Context triple: [EB-1 priority workers immigrant visa, selfPetitionAllowedForEB1A, yes]
  • A. canBePetitionedBy
    Indicates that an entity is eligible to receive formal petitions, requests, or appeals from another entity.
  • B. appliesToCitizenshipStatus
    Indicates that something (such as a rule, benefit, restriction, or condition) is relevant to or governs individuals based on their citizenship status.
  • C. containsPetition
    Indicates that one entity includes or holds a petition within it, either as content or as a component.
  • D. appliedFor
    Indicates that an entity has submitted a request or application to another entity for a position, service, benefit, or opportunity.
  • E. mayHoldCitizenshipOf
    Indicates that an entity is allowed or eligible to possess citizenship status of a specified country or jurisdiction.
  • 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_69d81c5ba13c8190839315f54768acfd completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02dc9f488190b7181dcb7e304632 completed April 14, 2026, 9:03 a.m.
PD Predicate disambiguation batch_69dbc8691b608190a25a7c70a366b170 completed April 12, 2026, 4:29 p.m.
PDg Predicate description generation batch_69dcad0eea9881908f71e1eed9a2446b completed April 13, 2026, 8:45 a.m.
Created at: April 9, 2026, 10:14 p.m.