Triple
T15515062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. nationals |
E368813
|
entity |
| Predicate | canWork |
P41675
|
FINISHED |
| Object | in the United States without employment authorization as an alien |
—
|
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: in the United States without employment authorization as an alien | Statement: [U.S. nationals, canWork, in the United States without employment authorization as an alien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canWork Context triple: [U.S. nationals, canWork, in the United States without employment authorization as an alien]
-
A.
mayWorkIn
chosen
Indicates that an entity is allowed or has the possibility to work in a particular place, organization, or context.
-
B.
respondsToWork
Indicates that one entity replies or reacts to another entity’s work, output, or contribution.
-
C.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
D.
canTask
Indicates that an entity has the ability or permission to perform a specified task.
-
E.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04031e62c8190953b61207142af15 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:02 a.m.