Triple
T15541699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 45: Iwayaji |
E370493
|
entity |
| Predicate | hasPilgrimageStampOffice |
P113870
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Temple 45: Iwayaji, hasPilgrimageStampOffice, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimageStampOffice Context triple: [Temple 45: Iwayaji, hasPilgrimageStampOffice, yes]
-
A.
hasPilgrimageStamp
chosen
Indicates that an entity possesses or has received a stamp documenting participation in a pilgrimage.
-
B.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
-
C.
pilgrimageCredentialOffice
Indicates the office or authority responsible for issuing, validating, or managing official credentials for pilgrims undertaking a pilgrimage.
-
D.
hasPilgrimageRegion
Indicates that an entity is associated with a specific region that serves as the destination or location for its pilgrimage activities.
-
E.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
- 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.