Triple
T11266731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shitennoji Temple |
E266704
|
entity |
| Predicate | reasonForReconstruction |
P59732
|
FINISHED |
| Object | fires |
—
|
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: fires | Statement: [Shitennoji Temple, reasonForReconstruction, fires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForReconstruction Context triple: [Shitennoji Temple, reasonForReconstruction, fires]
-
A.
restorationReason
chosen
Indicates the reason or justification for which something that was previously removed, disabled, or altered has been restored to its former state.
-
B.
reconstructionFor
Indicates that one entity serves as a reconstruction, restoration, or rebuilt version of another entity.
-
C.
hasReconstructionPurpose
Indicates that something exists or is performed with the specific aim or function of reconstruction (e.g., rebuilding, restoring, or re-creating something).
-
D.
reconstructionInitiatedBy
Indicates that a reconstruction process or activity is started or triggered by a particular agent or entity.
-
E.
reconstructs
Indicates performing an action to rebuild, restore, or reassemble something from its parts, damage, or prior state.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94e5e3c8190a31995d55d20d7ed |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.