Triple
T9435452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iwashimizu Hachimangū |
E227492
|
entity |
| Predicate | rankInShintoShrines |
P44760
|
FINISHED |
| Object | one of the three great Hachiman shrines |
—
|
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: one of the three great Hachiman shrines | Statement: [Iwashimizu Hachimangū, rankInShintoShrines, one of the three great Hachiman shrines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInShintoShrines Context triple: [Iwashimizu Hachimangū, rankInShintoShrines, one of the three great Hachiman shrines]
-
A.
shrineRank
chosen
Indicates the hierarchical or status level assigned to a shrine relative to other shrines.
-
B.
numberOfShrines
Indicates the total count of shrines associated with a given entity or context.
-
C.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
-
D.
AtsutaShrineIs
Indicates that something has the status, identity, or defining characteristics of Atsuta Shrine.
-
E.
shrineType
Indicates the specific category or kind of shrine associated with an 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e64109081908222f590928bc572 |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:50 p.m.