Triple
T418038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Stuyvesant |
E8037
|
entity |
| Predicate | causeOfInjury |
P14656
|
FINISHED |
| Object | battle in the Caribbean |
—
|
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: battle in the Caribbean | Statement: [Peter Stuyvesant, causeOfInjury, battle in the Caribbean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfInjury Context triple: [Peter Stuyvesant, causeOfInjury, battle in the Caribbean]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
hasInjuries
Indicates that an entity has sustained one or more physical or bodily injuries.
-
C.
accidentType
Indicates the specific category or kind of accident associated with an event or incident.
-
D.
causeOfDisability
Indicates that one entity is the reason or source that brings about another entity’s disability.
-
E.
fatalInjury
Indicates that an entity causes or sustains an injury that directly results in death.
- F. None of above. chosen
Provenance (4 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd1ca148190a66bd8c5aad867d5 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb8545c8190a2b8517e7ed5b92e |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.