Triple
T9834857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Migration Agency |
E239073
|
entity |
| Predicate | handlesApplicationsFrom |
P83634
|
FINISHED |
| Object | foreign nationals |
—
|
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: foreign nationals | Statement: [Swedish Migration Agency, handlesApplicationsFrom, foreign nationals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesApplicationsFrom Context triple: [Swedish Migration Agency, handlesApplicationsFrom, foreign nationals]
-
A.
handlesApplicationsForLevel
Indicates that an entity is responsible for processing or managing applications associated with a specific level (such as grade, tier, or stage).
-
B.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
C.
applicationProcessedBy
chosen
Indicates that an application has been handled or dealt with by a particular agent or system.
-
D.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
-
E.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb339aa1c8190901d8e660cef49c5 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.