Triple
T37913638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 曹洞宗 |
E945751
|
entity |
| Predicate | 日本における中興の祖 |
P124404
|
FINISHED |
| Object | 瑩山紹瑾 |
—
|
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: 瑩山紹瑾 | Statement: [曹洞宗, 日本における中興の祖, 瑩山紹瑾]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 日本における中興の祖 Context triple: [曹洞宗, 日本における中興の祖, 瑩山紹瑾]
-
A.
successorAsDaimyoOfHikone
Indicates that one entity became the next daimyō (feudal lord) of Hikone, directly succeeding another in that position.
-
B.
shogunateName
Indicates the name assigned to a particular shogunate.
-
C.
founderInJapan
chosen
Indicates that an entity is the founder of something (such as an organization or company) specifically in Japan.
-
D.
formerJapaneseNameOf
Indicates that one entity was previously used as the Japanese name for another entity but is no longer its current Japanese name.
-
E.
successorInJapan
Indicates that one entity directly follows or replaces another in a role, position, or sequence within the context of Japan.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.