Triple
T2524428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fushimi Inari Taisha |
E56000
|
entity |
| Predicate | toriiDonatedBy |
P39656
|
FINISHED |
| Object | individual worshippers |
—
|
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: individual worshippers | Statement: [Fushimi Inari Taisha, toriiDonatedBy, individual worshippers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toriiDonatedBy Context triple: [Fushimi Inari Taisha, toriiDonatedBy, individual worshippers]
-
A.
hasTorii
Indicates that something possesses or features a torii gate as part of its structure or environment.
-
B.
AtsutaShrineIs
Indicates that something has the status, identity, or defining characteristics of Atsuta Shrine.
-
C.
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.
-
D.
numberOfMainTorii
Indicates the specific count of primary torii gates associated with a given entity.
-
E.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd252f1c88190ac93604542f80f49 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1487e0c8190b90dcf30586ad4cd |
completed | March 7, 2026, 7:18 a.m. |
Created at: March 6, 2026, 9:46 p.m.