Triple
T20809210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pub.L. 89-732 |
E512250
|
entity |
| Predicate | appliesToEntryStatus |
P1129
|
FINISHED |
| Object | admitted aliens |
—
|
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: admitted aliens | Statement: [Pub.L. 89-732, appliesToEntryStatus, admitted aliens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToEntryStatus Context triple: [Pub.L. 89-732, appliesToEntryStatus, admitted aliens]
-
A.
appliedToStatus
Indicates that an action, rule, or condition is associated with or affects a particular status or state.
-
B.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
C.
serviceEntryStatus
Indicates the current state or condition of a service entry within a process or system (e.g., whether it is active, pending, completed, or otherwise classified).
-
D.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
E.
isStatusOf
Indicates that a particular status or condition is assigned to, or characterizes, a specific entity.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d199888190b8b190c928f510b7 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.