Triple
T36128000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UJN |
E1044934
|
entity |
| Predicate | internationalStudentProgram |
P18227
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [UJN, internationalStudentProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internationalStudentProgram Context triple: [UJN, internationalStudentProgram, yes]
-
A.
internationalProgram
Indicates a program that involves participation, collaboration, or exchange across multiple countries or international boundaries.
-
B.
offersInternationalPrograms
chosen
Indicates that an institution or organization provides programs or courses available to participants from other countries or across national borders.
-
C.
internationalStudentsShare
Indicates the proportion or percentage of a population or group that consists of international students.
-
D.
offersStudyAbroad
Indicates that an institution or program provides opportunities for participants to study in a foreign country.
-
E.
hasInternationalStudents
Indicates that an institution or organization includes students who come from countries other than the one in which it is located.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:08 p.m.