Triple
T4593994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSx Program |
E103563
|
entity |
| Predicate | admissionBasis |
P43396
|
FINISHED |
| Object | selective admission |
—
|
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: selective admission | Statement: [MSx Program, admissionBasis, selective admission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionBasis Context triple: [MSx Program, admissionBasis, selective admission]
-
A.
admissionsBasedOn
chosen
Indicates that acceptance or entry decisions are determined according to specified criteria, factors, or conditions.
-
B.
admissionType
Indicates the category or manner in which an entity (such as a person or case) is formally accepted or admitted into a system, institution, or process.
-
C.
admissionsSystem
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
D.
admissionsLevel
Indicates the degree or category of access, entry, or acceptance granted in an admissions context.
-
E.
officialAdmissionBy
Indicates that an entity is formally accepted, enrolled, or granted entry by an authorized official or institution.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd593e115081909b11149e02fe4ef3 |
completed | March 20, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.