Triple
T22580778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 学習院大学政経学部 |
E544559
|
entity |
| Predicate | 所在国の教育制度 |
P124658
|
FINISHED |
| Object | 日本の大学教育制度 |
—
|
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: 日本の大学教育制度 | Statement: [学習院大学政経学部, 所在国の教育制度, 日本の大学教育制度]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 所在国の教育制度 Context triple: [学習院大学政経学部, 所在国の教育制度, 日本の大学教育制度]
-
A.
hasPublicEducationSystem
Indicates that a governing body or region maintains an organized, state-funded system of schools and educational institutions accessible to the general public.
-
B.
hasOwnEducationSystem
Indicates that one entity possesses and administers its own distinct education system, separate from those of other entities.
-
C.
introducedEducationSystem
Indicates that an entity established or brought a particular education system into use for another entity or context.
-
D.
isInEducationalSystemOf
chosen
Indicates that one entity belongs to, is administered by, or operates within the educational system governed by another entity.
-
E.
educationSystem
Indicates the relationship in which an entity is part of, governed by, or operates within a particular system or structure of education.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15ff065308190bca9fb24b47757e6 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.