Triple
T11549758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honden (main hall) |
E273858
|
entity |
| Predicate | linkedRitualObject |
P7123
|
FINISHED |
| Object | go-shintai |
—
|
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: go-shintai | Statement: [Honden (main hall), linkedRitualObject, go-shintai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRitualObject Context triple: [Honden (main hall), linkedRitualObject, go-shintai]
-
A.
hasRitualObject
chosen
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
B.
relatedRitual
Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
-
C.
appearsInRitual
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
D.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
E.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e615b08190a072924329a94a6a |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.