Triple
T22440183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 上皇 |
E554732
|
entity |
| Predicate | ceremonialInvolvement |
P112273
|
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: [上皇, ceremonialInvolvement, 一部の公的行事に参加することがある]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialInvolvement Context triple: [上皇, ceremonialInvolvement, 一部の公的行事に参加することがある]
-
A.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
B.
ceremonialRoleInvolves
chosen
Indicates that a ceremonial role includes or entails performing a particular action, duty, or function as part of that ceremony.
-
C.
ceremonialAssociation
Indicates a relationship where entities are linked through participation in, role within, or connection to a formal ceremony or ritual event.
-
D.
ceremonialAction
Indicates an action performed as part of a formal ceremony or ritual, typically following prescribed traditions or symbolic procedures.
-
E.
ceremonialFocus
Indicates that one entity serves as the central object, site, or theme around which a ceremony or ritual is organized or directed.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae0edcc8190919b198035de0df2 |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.