Triple
T26024416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kami |
E647250
|
entity |
| Predicate | areReveredAs |
P137926
|
FINISHED |
| Object | sacred forces |
—
|
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: sacred forces | Statement: [kami, areReveredAs, sacred forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areReveredAs Context triple: [kami, areReveredAs, sacred forces]
-
A.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
B.
respectedAs
Indicates that one entity regards another with esteem or honor, recognizing their value, status, or authority.
-
C.
isVeneratedAs
chosen
Indicates that one entity is regarded and honored by others as sacred, holy, or worthy of deep reverence.
-
D.
veneratedBefore
Indicates that one entity was honored or revered at an earlier time or prior to another entity.
-
E.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605ea27648190b481ce5a9c0aef22 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:05 a.m.