Triple
T9435460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iwashimizu Hachimangū |
E227492
|
entity |
| Predicate | mainHallRebuiltIn |
P11204
|
FINISHED |
| Object | 1634 |
—
|
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: 1634 | Statement: [Iwashimizu Hachimangū, mainHallRebuiltIn, 1634]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainHallRebuiltIn Context triple: [Iwashimizu Hachimangū, mainHallRebuiltIn, 1634]
-
A.
rebuiltAsPalace
Indicates that a structure or building was reconstructed or transformed into a palace.
-
B.
towerRebuiltBy
Indicates that a tower was reconstructed or restored through the actions or efforts of a specified agent or entity.
-
C.
rebuiltOrExpanded
Indicates that one entity has been reconstructed, enlarged, or otherwise significantly developed from its previous form or state.
-
D.
largelyRebuilt
chosen
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
E.
hasRebuiltHistoricCenter
Indicates that an entity has undertaken and completed the restoration or reconstruction of a historic city or town center.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e64109081908222f590928bc572 |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:50 p.m.