Triple
T36127742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōmiwa Jinja |
E1044928
|
entity |
| Predicate | hasToriiLocation |
P25751
|
FINISHED |
| Object | approach to Mount Miwa |
—
|
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: approach to Mount Miwa | Statement: [Ōmiwa Jinja, hasToriiLocation, approach to Mount Miwa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasToriiLocation Context triple: [Ōmiwa Jinja, hasToriiLocation, approach to Mount Miwa]
-
A.
hasTorii
chosen
Indicates that something possesses or features a torii gate as part of its structure or environment.
-
B.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
C.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
D.
hasToriiType
Indicates that one entity is characterized by or associated with a specific type or style of torii (traditional Japanese gate).
-
E.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of another 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4:08 p.m.