Triple
T7168923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U visa |
E167142
|
entity |
| Predicate | legalStatusProvided |
P2250
|
FINISHED |
| Object | temporary lawful status |
—
|
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: temporary lawful status | Statement: [U visa, legalStatusProvided, temporary lawful status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusProvided Context triple: [U visa, legalStatusProvided, temporary lawful status]
-
A.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
B.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
C.
usedLegalStatus
Indicates that one entity applies or relies on the legal status or classification of another entity in a given context.
-
D.
legalStatusNote
Indicates a note or comment that provides additional information or clarification about the legal status of something.
-
E.
legalStatusVariesBy
Indicates that the legal status of something differs depending on a specified jurisdiction, context, or set of conditions.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85c606081909f76d76fc5b90bc8 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.