Triple
T30930299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish universities |
E787974
|
entity |
| Predicate | admissionsPortal |
P33885
|
FINISHED |
| Object | Universityadmissions.se |
—
|
NE NERFINISHED |
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: Universityadmissions.se | Statement: [Swedish universities, admissionsPortal, Universityadmissions.se]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionsPortal Context triple: [Swedish universities, admissionsPortal, Universityadmissions.se]
-
A.
admissionsSystem
chosen
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
B.
admissionsPath
Indicates the route, process, or sequence of steps through which an entity gains admission to an institution, program, or service.
-
C.
admissionsScope
Indicates the extent or boundaries of what is included or covered within an admissions process or policy.
-
D.
admissionsBasedOn
Indicates that acceptance or entry decisions are determined according to specified criteria, factors, or conditions.
-
E.
admissionsStage
Indicates the specific phase or step an entity is currently in within an admissions or application process.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692e0113c8190b5b207b7e5182ee0 |
completed | May 3, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:52 p.m.