Triple
T236583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Havana (1762) |
E4836
|
entity |
| Predicate | notableDisease |
P1481
|
FINISHED |
| Object | yellow fever |
—
|
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: yellow fever | Statement: [Siege of Havana (1762), notableDisease, yellow fever]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDisease Context triple: [Siege of Havana (1762), notableDisease, yellow fever]
-
A.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
B.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notablyAssociatedWith
chosen
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
E.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25ccc5d548190b505bf1d99db41bd |
completed | Feb. 28, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69a25b5dc640819092669575731c393f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.