Triple
T34634833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yushima Tenmangu Shrine |
E889392
|
entity |
| Predicate | rededicationCentury |
P3370
|
FINISHED |
| Object | 14th century |
—
|
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: 14th century | Statement: [Yushima Tenmangu Shrine, rededicationCentury, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rededicationCentury Context triple: [Yushima Tenmangu Shrine, rededicationCentury, 14th century]
-
A.
dedicationCenturyOfSaint
Indicates the century in which a saint to whom something is dedicated (such as a church or shrine) lived or is traditionally associated.
-
B.
rededicationDate
chosen
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
-
C.
rededicationPossible
Indicates that conditions are such that a prior commitment, structure, or resource can be formally renewed or dedicated again.
-
D.
rededicatedBy
Indicates that something has been dedicated again or anew by a particular agent or entity.
-
E.
laterRededicatedTo
Indicates that something was originally dedicated to one purpose or entity and, at a later time, was dedicated again to a different purpose or 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.