Triple
T36431129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hopkins Manuscript |
E897443
|
entity |
| Predicate | hasMainCatastropheType |
P64317
|
FINISHED |
| Object | astronomical disaster |
—
|
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: astronomical disaster | Statement: [The Hopkins Manuscript, hasMainCatastropheType, astronomical disaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCatastropheType Context triple: [The Hopkins Manuscript, hasMainCatastropheType, astronomical disaster]
-
A.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
B.
typeOfDisaster
Indicates that one entity is classified as a specific kind or category of disaster in relation to another entity.
-
C.
notableDisasterType
chosen
Indicates the specific kind or category of disaster for which something (such as a place, event, or entity) is notable or best known.
-
D.
hasDisasterElement
Indicates that something includes, involves, or is characterized by an element or aspect of a disaster.
-
E.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a033ed9322c8190be994a8d99761caa |
completed | May 12, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_6a033df2b254819082a672859e5168e6 |
completed | May 12, 2026, 2:49 p.m. |
Created at: May 3, 2026, 4:10 p.m.