Triple
T24656236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaneiji Temple |
E610398
|
entity |
| Predicate | foundingRulerPatron |
P114568
|
FINISHED |
| Object | Tokugawa Ieyasu |
—
|
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: Tokugawa Ieyasu | Statement: [Kaneiji Temple, foundingRulerPatron, Tokugawa Ieyasu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingRulerPatron Context triple: [Kaneiji Temple, foundingRulerPatron, Tokugawa Ieyasu]
-
A.
patronRuler
chosen
Indicates a relationship where one entity serves as a protective or sponsoring ruler or sovereign authority over another.
-
B.
royalHouseFounder
Indicates that one entity is the person who founded or established the royal house or dynasty to which the other entity belongs.
-
C.
roleInDynastyFounding
Indicates the role or contribution an entity had in the founding or establishment of a particular dynasty.
-
D.
founderOfPredecessor
Indicates that an entity is the founder of another entity that served as a predecessor to a specified organization or institution.
-
E.
fatherIsRulerOf
Indicates that the person who is the father holds the position of ruler or sovereign over the specified entity or domain.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.