Triple
T36936758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 台北帝国大学 |
E913640
|
entity |
| Predicate | campusContinuity |
P147692
|
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: [台北帝国大学, campusContinuity, 主要施設が国立台湾大学に引き継がれた]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusContinuity Context triple: [台北帝国大学, campusContinuity, 主要施設が国立台湾大学に引き継がれた]
-
A.
campusContinuesAs
chosen
Indicates that one campus location or institution persists, evolves, or is carried forward as another campus in a subsequent form or time.
-
B.
campus
Indicates that an entity is located on, associated with, or taking place within a particular campus.
-
C.
campusSystem
Indicates a relationship where an educational institution is part of, managed by, or operates within a particular campus system or network.
-
D.
governsCampus
Indicates that one entity has administrative or authoritative control over the operations and policies of a campus.
-
E.
campus1
Indicates a relationship where an entity is identified as a campus or is located on/associated with a particular campus.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdfc6a1c8190ba9fd414a889fc72 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.