Triple
T7112086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T visa |
E165729
|
entity |
| Predicate | derivativeCategory |
P29520
|
FINISHED |
| Object | T-2 spouse of a T-1 nonimmigrant |
—
|
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: T-2 spouse of a T-1 nonimmigrant | Statement: [T visa, derivativeCategory, T-2 spouse of a T-1 nonimmigrant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivativeCategory Context triple: [T visa, derivativeCategory, T-2 spouse of a T-1 nonimmigrant]
-
A.
derivativeDesignation
chosen
Indicates that one entity is formally identified as a derivative or adapted version of another entity.
-
B.
differential
Indicates a relationship where one quantity or state is defined as the infinitesimal change or difference relative to another variable or function.
-
C.
hasDerivatives
Indicates that one entity is derived, obtained, or developed from another entity.
-
D.
hasDerivative
Indicates that one entity is derived, obtained, or produced from another through some transformation, process, or modification.
-
E.
categoryDistinguishedFrom
Indicates that one category is explicitly distinguished from another, clarifying that they are separate and should not be confused.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5edf89c8190a069b35ff7768165 |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.