Triple
T15541712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 46: Jōruriji |
E370494
|
entity |
| Predicate | templeNumberOnShikokuPilgrimage |
P113865
|
FINISHED |
| Object | 46 |
—
|
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: 46 | Statement: [Temple 46: Jōruriji, templeNumberOnShikokuPilgrimage, 46]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeNumberOnShikokuPilgrimage Context triple: [Temple 46: Jōruriji, templeNumberOnShikokuPilgrimage, 46]
-
A.
pilgrimageTempleCount
Indicates the number of temples associated with or visited during a particular pilgrimage.
-
B.
numberOfShrines
Indicates the total count of shrines associated with a given entity or context.
-
C.
positionInShikokuPilgrimage
chosen
Indicates the specific sequential position an entity holds along the route of the Shikoku pilgrimage.
-
D.
isNumberedTempleOf
Indicates that one entity is a specific, designated temple identified by a particular number within a series or system associated with another entity.
-
E.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04432c3808190bb5b653bf8de30c6 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.