Triple
T5455153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. John’s University, Shanghai |
E122460
|
entity |
| Predicate | admissionSelectivity |
P738
|
FINISHED |
| Object | highly selective |
—
|
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: highly selective | Statement: [St. John’s University, Shanghai, admissionSelectivity, highly selective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionSelectivity Context triple: [St. John’s University, Shanghai, admissionSelectivity, highly selective]
-
A.
typicalAdmissionSelectivity
chosen
Indicates the usual level of competitiveness or restrictiveness in admitting applicants to an institution or program.
-
B.
admissionsBasedOn
Indicates that acceptance or entry decisions are determined according to specified criteria, factors, or conditions.
-
C.
admissionsLevel
Indicates the degree or category of access, entry, or acceptance granted in an admissions context.
-
D.
admissionsSystem
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
E.
controlsAdmissionsFor
Indicates that one entity has authority or responsibility over managing and deciding admissions for another entity.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.