Triple
T881220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Graduate School of Business |
E19029
|
entity |
| Predicate | admissionsCriteria |
P58
|
FINISHED |
| Object | GMAT or GRE |
—
|
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: GMAT or GRE | Statement: [Stanford Graduate School of Business, admissionsCriteria, GMAT or GRE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionsCriteria Context triple: [Stanford Graduate School of Business, admissionsCriteria, GMAT or GRE]
-
A.
eligibilityCriteria
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
-
B.
admissionPolicy
chosen
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
-
C.
typicalAdmissionSelectivity
Indicates the usual level of competitiveness or restrictiveness in admitting applicants to an institution or program.
-
D.
admissionOrder
Indicates the sequence or priority in which admissions occur or are processed relative to one another.
-
E.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4accb653c81909fe0753f78145be9 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8eca748190b58e0f08b30fba43 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.