Triple
T36225607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Danish Arabia Expedition |
E1047974
|
entity |
| Predicate | causeOfDeathOfMembers |
P144
|
FINISHED |
| Object | disease |
—
|
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: disease | Statement: [Royal Danish Arabia Expedition, causeOfDeathOfMembers, disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDeathOfMembers Context triple: [Royal Danish Arabia Expedition, causeOfDeathOfMembers, disease]
-
A.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
causeOfDeathsCommemorated
Indicates that one entity is the cause of the deaths that are formally remembered or honored by another entity.
-
C.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
D.
deifiedPersonDeathCause
Indicates the cause or manner of death of the person who is venerated or treated as a deity.
-
E.
namedAfterCauseOfDeath
Indicates that an entity is named after the cause of death of a person or organism.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:09 p.m.