Triple
T19383807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest University Canada |
E484877
|
entity |
| Predicate | hadInternationalStudents |
P16422
|
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: [Quest University Canada, hadInternationalStudents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadInternationalStudents Context triple: [Quest University Canada, hadInternationalStudents, yes]
-
A.
hasInternationalStudents
chosen
Indicates that an institution or organization includes students who come from countries other than the one in which it is located.
-
B.
internationalStudentsShare
Indicates the proportion or percentage of a population or group that consists of international students.
-
C.
hasStudyAbroad
Indicates that an entity has participated in or completed a study-abroad experience in another country.
-
D.
internationalProgram
Indicates a program that involves participation, collaboration, or exchange across multiple countries or international boundaries.
-
E.
hadInternationalComponentIn
Indicates that an event, activity, or entity included a significant international element or involvement during a specified time or context.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a626b288190a27a30deb0ccabc3 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.