Triple
T26020938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form I-918, Supplement B |
E647150
|
entity |
| Predicate | notCompletedBy |
P78572
|
FINISHED |
| Object | the U visa applicant |
—
|
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: the U visa applicant | Statement: [Form I-918, Supplement B, notCompletedBy, the U visa applicant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notCompletedBy Context triple: [Form I-918, Supplement B, notCompletedBy, the U visa applicant]
-
A.
hasNotCompleted
chosen
Indicates that an entity has an expected task, process, or requirement that remains unfinished or not yet fulfilled.
-
B.
alsoCompletedBy
Indicates that the same task, activity, or item has been completed by an additional agent or entity besides the one already referenced.
-
C.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
notResolvedBy
Indicates that an issue, problem, or request remains unresolved despite the involvement or actions of a specified entity.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605e5af4081909e3862d44e313d7f |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:03 a.m.