Triple
T8709980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypocenter Park |
E206749
|
entity |
| Predicate | groundZeroOf |
P65427
|
FINISHED |
| Object | atomic bombing of Nagasaki |
—
|
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: atomic bombing of Nagasaki | Statement: [Hypocenter Park, groundZeroOf, atomic bombing of Nagasaki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundZeroOf Context triple: [Hypocenter Park, groundZeroOf, atomic bombing of Nagasaki]
-
A.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
B.
groundComponent
Indicates that one entity serves as a foundational or base part upon which another entity is built, attached, or functionally dependent.
-
C.
groundService
Indicates that one entity provides ground-based operational support or services to another entity, typically in a transportation or logistics context.
-
D.
elevationBelowGround
Indicates that one entity’s elevation is located beneath the ground surface or reference ground level.
-
E.
formsZeroPointFor
chosen
Indicates that one entity serves as the reference or origin point (zero point) for measuring or defining another 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3034708190b895eaf890d62198 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.