Triple

T32112073
Position Surface form Disambiguated ID Type / Status
Subject Special Category Visa (subclass 444) E820143 entity
Predicate visaCeasesWhen P173575 FINISHED
Object holder departs Australia 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: holder departs Australia | Statement: [Special Category Visa (subclass 444), visaCeasesWhen, holder departs Australia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: visaCeasesWhen
Context triple: [Special Category Visa (subclass 444), visaCeasesWhen, holder departs Australia]
  • A. visaClass
    Indicates the specific category or type of visa associated with an individual or immigration case.
  • B. visaRequirement
    Indicates whether one party must obtain a visa in order to enter, stay in, or transit through the territory of another party.
  • C. shareVisaPolicy
    Indicates that two entities apply the same or highly similar visa requirements and entry rules to travelers.
  • D. passportRevokedBy
    Indicates that an authority or entity has officially canceled or withdrawn the validity of a person's passport.
  • E. illegalityStatusAtDeparture
    Indicates whether an entity’s departure from a location or jurisdiction was illegal at the time it occurred.
  • 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_69f3490209c881908ec0241476715f15 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b903538481909cffcb6cc1cc0e70 completed May 3, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69f6b3a970b0819090c6473844ffa8e3 completed May 3, 2026, 2:32 a.m.
PDg Predicate description generation batch_69f6b49339048190b617a6749f648825 completed May 3, 2026, 2:36 a.m.
Created at: May 1, 2026, 12:27 a.m.