Triple
T27160145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurozumi Munetada |
E682637
|
entity |
| Predicate | religiousPracticePromoted |
P29871
|
FINISHED |
| Object | sun veneration |
—
|
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: sun veneration | Statement: [Kurozumi Munetada, religiousPracticePromoted, sun veneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousPracticePromoted Context triple: [Kurozumi Munetada, religiousPracticePromoted, sun veneration]
-
A.
practicesReligion
Indicates that an entity actively follows, observes, or participates in the beliefs, rituals, and customs of a particular religion.
-
B.
promotedReligion
chosen
Indicates that an entity actively supported, advocated for, or worked to spread a particular religion.
-
C.
religiousActivity
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
D.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
E.
religiousTransmission
Indicates the passing on or spread of religious beliefs, practices, or traditions from one entity to another.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 9:18 a.m.