Triple
T13857654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-1B specialty occupation visa |
E333105
|
entity |
| Predicate | maximumTypicalStay |
P50746
|
FINISHED |
| Object | six years |
—
|
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: six years | Statement: [H-1B specialty occupation visa, maximumTypicalStay, six years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTypicalStay Context triple: [H-1B specialty occupation visa, maximumTypicalStay, six years]
-
A.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
B.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
C.
residencyDuration
chosen
Indicates the length of time an entity has continuously resided or stayed in a particular place or jurisdiction.
-
D.
propertyType_maxptime
Indicates the maximum allowed or configured time duration associated with a given property type.
-
E.
hasTypicalVisitDuration
Indicates the usual or expected length of time that a visit to something typically lasts.
- 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_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. |
Created at: April 9, 2026, 10:14 p.m.