Triple
T14383285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 20: Kakurinji |
E356659
|
entity |
| Predicate | numberInShikokuPilgrimage |
P16195
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Temple 20: Kakurinji, numberInShikokuPilgrimage, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInShikokuPilgrimage Context triple: [Temple 20: Kakurinji, numberInShikokuPilgrimage, 20]
-
A.
numberOfShrines
Indicates the total count of shrines associated with a given entity or context.
-
B.
pilgrimageTempleCount
chosen
Indicates the number of temples associated with or visited during a particular pilgrimage.
-
C.
eraNumberInJapan
Indicates the specific numbered position of a historical era within the sequence of Japanese eras.
-
D.
ichinomiya
Indicates a relationship where a location or institution holds the status of "Ichinomiya," the primary or highest-ranking Shinto shrine of a historical province.
-
E.
terminusOnHonshu
Indicates that the endpoint or terminus of something (such as a route, line, or connection) is located on the island of Honshu.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900d28c88190a37feee4743563de |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.