Triple
T23413866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天皇が新穀を親しく食す |
E560149
|
entity |
| Predicate | performedInCapacity |
P32677
|
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: [天皇が新穀を親しく食す, performedInCapacity, 祭祀主宰者としての天皇]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedInCapacity Context triple: [天皇が新穀を親しく食す, performedInCapacity, 祭祀主宰者としての天皇]
-
A.
performedUnder
Indicates that an action or task was carried out subject to, or within the scope of, a particular condition, authority, context, or framework.
-
B.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
C.
heldByInCapacityAs
chosen
Indicates that something is held or possessed by an entity specifically in a defined role, function, or official capacity rather than in a general or personal sense.
-
D.
hadCapacity
Indicates that an entity possessed the ability, resources, or potential to perform a particular function or action.
-
E.
performedTo
Indicates that an action or performance is directed toward or carried out on 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a513502881909f33a43bfd5e63a7 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.