Triple
T28514910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J-1 Exchange Visitor Program |
E721586
|
entity |
| Predicate | dependentStatus |
P125582
|
FINISHED |
| Object | J-2 |
—
|
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: J-2 | Statement: [J-1 Exchange Visitor Program, dependentStatus, J-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dependentStatus Context triple: [J-1 Exchange Visitor Program, dependentStatus, J-2]
-
A.
designationStatus
Indicates the current official classification or standing assigned to an entity within a defined system or process.
-
B.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
C.
statusDependsOn
chosen
Indicates that the status or state of one entity is determined or influenced by the status or state of another entity.
-
D.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f78a2f48190b134be8272852b78 |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:16 a.m.