Triple
T37352584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-1 visa |
E927363
|
entity |
| Predicate | requiresBackgroundChecks |
P52859
|
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, requiresBackgroundChecks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBackgroundChecks Context triple: [K-1 visa, requiresBackgroundChecks, yes]
-
A.
mayRequireBackgroundIn
Indicates that performing or understanding one entity may necessitate prior knowledge, experience, or qualifications in another domain or subject.
-
B.
requiredBackgroundCheck
chosen
Indicates that an entity must undergo or has undergone a mandatory background check as a condition for participation, access, or approval in relation to another entity.
-
C.
requiresCheckAgainst
Indicates that one entity must be verified, validated, or compared against another entity before proceeding.
-
D.
hasBackground
Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
-
E.
requiresCheckIn
Indicates that one entity must perform a check-in action or be checked in as a prerequisite for another entity, event, or process to proceed.
- 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_6a0042524d8c8190884a10fce669ae95 |
completed | May 10, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_6a0041e89bd881909e32764699bcb89b |
completed | May 10, 2026, 8:29 a.m. |
Created at: May 3, 2026, 4:16 p.m.