Triple

T32112067
Position Surface form Disambiguated ID Type / Status
Subject Special Category Visa (subclass 444) E820143 entity
Predicate holderMustMeet P176782 FINISHED
Object health requirements 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: health requirements | Statement: [Special Category Visa (subclass 444), holderMustMeet, health requirements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: holderMustMeet
Context triple: [Special Category Visa (subclass 444), holderMustMeet, health requirements]
  • A. holderMustHave chosen
    Indicates that the entity designated as the holder is required to possess or maintain the related entity or resource.
  • B. holderMustBe
    Indicates that a specified entity is required to be the holder or possessor of another entity or resource.
  • C. mustMeet
    Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
  • D. boardingRequirement
    Indicates the conditions or criteria that must be met for an entity to be allowed to board another entity (such as a vehicle, vessel, or aircraft).
  • E. requiresMember
    Indicates that one entity depends on or mandates the participation, presence, or inclusion of another entity as a member in order for a condition, action, or relationship to hold.
  • 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_69f3490209c881908ec0241476715f15 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6f8164698819090c1b471f1caa4c6 completed May 3, 2026, 7:24 a.m.
PD Predicate disambiguation batch_69f6f6619404819084662aef1238261c completed May 3, 2026, 7:16 a.m.
Created at: May 1, 2026, 12:27 a.m.