Triple
T36450645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yonezawa Castle |
E897997
|
entity |
| Predicate | dedicatedShrineHonors |
P174695
|
FINISHED |
| Object | Uesugi Kenshin |
—
|
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: Uesugi Kenshin | Statement: [Yonezawa Castle, dedicatedShrineHonors, Uesugi Kenshin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedShrineHonors Context triple: [Yonezawa Castle, dedicatedShrineHonors, Uesugi Kenshin]
-
A.
hasShrinesDedicated
chosen
Indicates that one entity has shrines that are dedicated to honoring or worshiping another entity.
-
B.
recognizedAsShrineBy
Indicates that something is regarded or designated as a shrine by a particular person, group, or authority.
-
C.
stateShrineOf
Indicates that one entity is officially designated as a state-recognized shrine associated with or located within another entity (typically a state or region).
-
D.
guardianShrineOf
Indicates a relationship where one entity serves as a protective or custodial shrine dedicated to another entity.
-
E.
associatedShrine
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.