Triple
T895296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gakushuin University |
E19329
|
entity |
| Predicate | admissions |
P738
|
FINISHED |
| Object | competitive entrance examinations |
—
|
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: competitive entrance examinations | Statement: [Gakushuin University, admissions, competitive entrance examinations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissions Context triple: [Gakushuin University, admissions, competitive entrance examinations]
-
A.
campus
Indicates that an entity is located on, associated with, or taking place within a particular campus.
-
B.
UNAdmissionDate
Indicates the date on which an entity was officially admitted as a member of the United Nations.
-
C.
university
Indicates that an educational institution of higher learning is associated with or attended by a given entity.
-
D.
academicAdvisor
Indicates that one entity serves as the academic advisor, providing formal guidance and oversight on academic matters, to another entity.
-
E.
typicalAdmissionSelectivity
chosen
Indicates the usual level of competitiveness or restrictiveness in admitting applicants to an institution or program.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad23d6e88190a2fb5e1e168a7b44 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.