Triple
T25744926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seian University of Art and Design |
E648318
|
entity |
| Predicate | mayAccept |
P105611
|
FINISHED |
| Object | international students |
—
|
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: international students | Statement: [Seian University of Art and Design, mayAccept, international students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAccept Context triple: [Seian University of Art and Design, mayAccept, international students]
-
A.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
B.
mayApprove
Indicates that an entity has the authority or permission to approve another entity or action, but is not required to do so.
-
C.
mayAdmit
chosen
Indicates that one entity has the permission or authority to allow another entity to enter, join, or be accepted into something.
-
D.
mayTake
Indicates that an entity is permitted or allowed to take, enroll in, or participate in another entity (such as a course, resource, or opportunity).
-
E.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1e9dd081908c70074c8aa49e51 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 3:49 a.m.