Triple
T26940608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiroshima Castle Park |
E678501
|
entity |
| Predicate | wasReconstructedIn |
P24909
|
FINISHED |
| Object | post–World War II era |
—
|
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: post–World War II era | Statement: [Hiroshima Castle Park, wasReconstructedIn, post–World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasReconstructedIn Context triple: [Hiroshima Castle Park, wasReconstructedIn, post–World War II era]
-
A.
wasReconstructed
Indicates that something previously existing was rebuilt or restored after damage, destruction, or alteration.
-
B.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
C.
reconstructedAfter
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
-
D.
reconstructedAsPartOf
Indicates that one entity has been rebuilt, restored, or recreated as a component or segment of another, larger whole.
-
E.
reconstructedDuring
chosen
Indicates that an entity was rebuilt, restored, or significantly repaired within a specified time period or event.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620531e28819086ffe00757f9743e |
completed | May 2, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:18 a.m.