Triple
T29975192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | けんこくきねんのひ |
E761423
|
entity |
| Predicate | 関連する歴史的出来事 |
P2107
|
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.
関係する国際的出来事
Indicates a relationship where something is connected to, involved in, or affected by an international event.
-
B.
associatedEpicEvent
Indicates that one entity is linked or connected to a particular epic event in a relevant or meaningful way.
-
C.
関連事件
Indicates a relationship where one event is connected or related to another event, typically as part of the same case, incident, or context.
-
D.
closelyAssociatedEvent
Indicates that one event is strongly related to, connected with, or occurs in close conjunction with another event.
-
E.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678d44b848190a0c7887baf01b905 |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:33 p.m.