Triple
T7990717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inari shrine |
E185997
|
entity |
| Predicate | hasSubshrineType |
P80216
|
FINISHED |
| Object | small roadside shrine |
—
|
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: small roadside shrine | Statement: [Inari shrine, hasSubshrineType, small roadside shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubshrineType Context triple: [Inari shrine, hasSubshrineType, small roadside shrine]
-
A.
hasSubTemple
Indicates that one temple includes or contains another temple as a subordinate or component temple within its structure or organization.
-
B.
hasRelicType
Indicates that an entity is associated with, classified by, or possesses a specific type or category of relic.
-
C.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
D.
hasRitualType
Indicates that an entity is associated with, or classified by, a particular type or category of ritual.
-
E.
hasHolinessType
Indicates a relationship where an entity is assigned or associated with a specific type or category of holiness.
- 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c6fc19c8190b98023e257c2f4f2 |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:16 p.m.