Triple
T27004665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konkō Daijin |
E680208
|
entity |
| Predicate | roleInKonkokyo |
P191880
|
FINISHED |
| Object | founder |
—
|
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: founder | Statement: [Konkō Daijin, roleInKonkokyo, founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInKonkokyo Context triple: [Konkō Daijin, roleInKonkokyo, founder]
-
A.
roleInShinto
Indicates that an entity holds a particular function, status, or significance within the context of Shinto beliefs, practices, or institutions.
-
B.
roleAtTemple
Indicates that an entity holds or performs a specific role, function, or position at a particular temple.
-
C.
roleInShinKokinWakashu
Indicates the specific role or involvement an entity has in relation to the Shin Kokin Wakashū (e.g., as compiler, editor, or contributor).
-
D.
roleInNichirenBuddhism
Indicates the specific function, position, or status an entity holds within the context of Nichiren Buddhism.
-
E.
roleInKojiki
Indicates the role or function an entity holds within the narrative or structure of the Kojiki.
- F. None of above. chosen
Provenance (4 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: April 27, 2026, 7 a.m.