Triple
T32161721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mizuko Kannon |
E821444
|
entity |
| Predicate | relatedRitualObject |
P7123
|
FINISHED |
| Object | small stone statues |
—
|
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: small stone statues | Statement: [Mizuko Kannon, relatedRitualObject, small stone statues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedRitualObject Context triple: [Mizuko Kannon, relatedRitualObject, small stone statues]
-
A.
relatedRitual
Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
-
B.
hasRitualObjectMaterial
Indicates that a ritual object is made from, composed of, or primarily constructed using a specified material.
-
C.
hasRitualObject
chosen
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
D.
ritualTools
Indicates that certain tools or objects are used in the performance or practice of a ritual.
-
E.
relicsAssociatedWith
Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:32 a.m.