Triple
T35175748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nantai-san |
E1015693
|
entity |
| Predicate | summitShrine |
P82250
|
FINISHED |
| Object | Okumiya of Futarasan Shrine |
—
|
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: Okumiya of Futarasan Shrine | Statement: [Nantai-san, summitShrine, Okumiya of Futarasan Shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitShrine Context triple: [Nantai-san, summitShrine, Okumiya of Futarasan Shrine]
-
A.
hasSummitShrines
chosen
Indicates that a location or geographic feature has shrines situated at or near its summit.
-
B.
isMostSacredShrineOf
Indicates that one entity is regarded as the holiest or most sacred shrine associated with another entity (such as a deity, religion, or tradition).
-
C.
shrineCity
Indicates that a city is the location of, or is associated with, a particular shrine.
-
D.
guardianShrineOf
Indicates a relationship where one entity serves as a protective or custodial shrine dedicated to another entity.
-
E.
summitShape
Indicates the geometric form or contour that characterizes the topmost point or summit of an object or landform.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d7625348190affc0770772de462 |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.