Triple
T30307267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One-Eyed Dragon of Ōshu |
E770818
|
entity |
| Predicate | refersToPersonWithReligion |
P27867
|
FINISHED |
| Object | Buddhist |
—
|
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: Buddhist | Statement: [One-Eyed Dragon of Ōshu, refersToPersonWithReligion, Buddhist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToPersonWithReligion Context triple: [One-Eyed Dragon of Ōshu, refersToPersonWithReligion, Buddhist]
-
A.
namedForPersonReligion
Indicates that something is named after a person specifically because of that person's religious identity, role, or significance.
-
B.
hasAssociatedReligion
chosen
Indicates that an entity is connected with or linked to a particular religion.
-
C.
relationshipToReligion
Indicates the nature or type of connection an entity has to a religion, such as affiliation, stance, or involvement.
-
D.
associatedReligionText
Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given religion.
-
E.
associatedReligionRole
Indicates that one entity holds a specific religious role, office, or function in relation to 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.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. |
Created at: April 29, 2026, 7:49 p.m.