Triple
T37352569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-1 visa |
E927363
|
entity |
| Predicate | requiresMedicalExam |
P184621
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [K-1 visa, requiresMedicalExam, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresMedicalExam Context triple: [K-1 visa, requiresMedicalExam, yes]
-
A.
requiresMedicalClearance
Indicates that one entity must obtain formal approval from a qualified medical authority before engaging in, accessing, or proceeding with the other entity or activity.
-
B.
hasExamination
chosen
Indicates that an entity is associated with, or undergoes, a specific examination or test.
-
C.
admissionRequired
Indicates that access to something is conditional on being formally admitted or granted entry beforehand.
-
D.
writtenExamRequiredBefore
Indicates that completing a written exam is a prerequisite that must occur before another specified action or event.
-
E.
examinedIn
Indicates that one entity is analyzed, inspected, or studied within the context, scope, or setting provided by another 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0041860fd081908623ef9fd40a9775 |
completed | May 10, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_6a00414b01488190a312adb3b25d69cf |
completed | May 10, 2026, 8:26 a.m. |
Created at: May 3, 2026, 4:16 p.m.