Triple
T32112082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Category Visa (subclass 444) |
E820143
|
entity |
| Predicate | visaSubclassNumber |
P173576
|
FINISHED |
| Object | 444 |
—
|
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: 444 | Statement: [Special Category Visa (subclass 444), visaSubclassNumber, 444]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visaSubclassNumber Context triple: [Special Category Visa (subclass 444), visaSubclassNumber, 444]
-
A.
visaNumberCategory
Indicates the classification or type category associated with a specific visa number.
-
B.
visaClass
Indicates the specific category or type of visa associated with an individual or immigration case.
-
C.
usedVisaType
Indicates that a particular type of visa was utilized in the context of an action, transaction, or event involving the related entities.
-
D.
modifiedVisaCategory
Indicates that an entity has changed or updated the classification or type of a visa associated with another entity.
-
E.
subclassificationStatus
Indicates the classification state or category assigned to a subclass within a broader classification system.
- 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.