Triple
T23793366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nachi Fire Festival |
E588467
|
entity |
| Predicate | honorsDeityOf |
P5606
|
FINISHED |
| Object | Nachi Falls |
—
|
NE NERFINISHED |
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: Nachi Falls | Statement: [Nachi Fire Festival, honorsDeityOf, Nachi Falls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsDeityOf Context triple: [Nachi Fire Festival, honorsDeityOf, Nachi Falls]
-
A.
honorsDeityAs
Indicates that one entity venerates, worships, or regards another entity as a particular deity or divine figure.
-
B.
hasDeity
chosen
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
C.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
-
D.
roleOfReferencedDeity
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
E.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6da693481908194cbc9d6a0bfef |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:40 p.m.