Triple
T4378641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yonsei |
E99070
|
entity |
| Predicate | isRelatedCohort |
P26016
|
FINISHED |
| Object | Gosei |
E435733
|
NE 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: Gosei | Statement: [Yonsei, isRelatedCohort, Gosei]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gosei Context triple: [Yonsei, isRelatedCohort, Gosei]
-
A.
Gosei
chosen
Gosei is a Japanese term referring to the fifth-generation descendants of Japanese emigrants living abroad.
-
B.
Gaimushō
Gaimushō is Japan’s Ministry of Foreign Affairs, responsible for managing the country’s diplomatic relations and international policies.
-
C.
Arinori
Arinori was a given name of Mori Arinori, a prominent Meiji-era Japanese statesman and reformer known for modernizing Japan’s education system.
-
D.
Seishirō
Seishirō is a Japanese given name commonly used for male individuals.
-
E.
Taihoku
Taihoku was the Japanese colonial-era name for Taipei, which served as the administrative and political center of Taiwan under Japanese rule.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35640269c8190a88fc6b59070561b |
completed | March 13, 2026, 12:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5f5e210108190bf14731ce3774b6b |
completed | March 14, 2026, 11:57 p.m. |
Created at: March 12, 2026, 11:18 p.m.