Triple
T11393757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Ledyard |
E269912
|
entity |
| Predicate | deathPlaceDuringEvent |
P21
|
FINISHED |
| Object | British attack on Fort Griswold in 1781 |
—
|
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: British attack on Fort Griswold in 1781 | Statement: [William Ledyard, deathPlaceDuringEvent, British attack on Fort Griswold in 1781]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathPlaceDuringEvent Context triple: [William Ledyard, deathPlaceDuringEvent, British attack on Fort Griswold in 1781]
-
A.
placeOfDeath
chosen
Indicates the location where an entity (typically a person or animal) died.
-
B.
deathDuringEvent
Indicates that an entity died while a specified event was occurring.
-
C.
traditionalPlaceOfDeath
Indicates the location where a person is customarily or culturally considered to have died, according to traditional or historical accounts.
-
D.
placeOfPassing
Indicates the location where an entity (typically a person) died or passed away.
-
E.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80018a58c81908b80dc9abd18d650 |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.