Triple
T37352587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-1 visa |
E927363
|
entity |
| Predicate | postMarriageStep |
P95303
|
FINISHED |
| Object | file adjustment of status for green card |
—
|
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: file adjustment of status for green card | Statement: [K-1 visa, postMarriageStep, file adjustment of status for green card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postMarriageStep Context triple: [K-1 visa, postMarriageStep, file adjustment of status for green card]
-
A.
marriedAfter
Indicates that one marriage occurred later in time than another specified marriage.
-
B.
marriageStatusChange
Indicates a change in an entity’s marital status from one state to another at a particular point in time.
-
C.
positionOnMarriage
Indicates a person's stance, opinion, or policy regarding the institution or practice of marriage.
-
D.
socialStatusAfterMarriage
Indicates the social status an individual holds as a result of, or following, their marriage.
-
E.
afterMarriageRole
chosen
Indicates the role or status an entity assumes following a marriage event.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.