Triple
T3173851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immigration Act of 1990 |
E66414
|
entity |
| Predicate | changedGroundsFor |
P6009
|
FINISHED |
| Object | inadmissibility |
—
|
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: inadmissibility | Statement: [Immigration Act of 1990, changedGroundsFor, inadmissibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedGroundsFor Context triple: [Immigration Act of 1990, changedGroundsFor, inadmissibility]
-
A.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
B.
hasGrounds
Indicates that one entity possesses or includes a physical area of land or outdoor space associated with it.
-
C.
reasonForChange
chosen
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
D.
changedAppealRoute
Indicates that the standard or expected process for appealing a decision has been altered from its original route.
-
E.
coversGrounds
Indicates that one entity extends over, occupies, or lies across the surface area of another entity (typically land or grounds).
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada670c800819098937783e2b05c7a |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.