Triple
T13857492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EB-1 priority workers immigrant visa |
E333102
|
entity |
| Predicate | preferenceCategory |
P65564
|
FINISHED |
| Object | first preference |
—
|
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: first preference | Statement: [EB-1 priority workers immigrant visa, preferenceCategory, first preference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferenceCategory Context triple: [EB-1 priority workers immigrant visa, preferenceCategory, first preference]
-
A.
statedPreference
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
B.
marketPreference
Indicates a relationship where one entity favors, targets, or prioritizes a particular market or market segment over others.
-
C.
unitPreference
Indicates a relationship where one entity specifies or favors a particular unit of measurement or representation over others.
-
D.
selectionCategory
chosen
Indicates the classification or grouping under which a particular selection or choice is categorized.
-
E.
currentPreference
Indicates the option, choice, or setting that an entity presently favors over alternatives at this moment in time.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.