Triple
T34570481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallabout Bay burial pits |
E887610
|
entity |
| Predicate | conditionOfBurials |
P121622
|
FINISHED |
| Object | bodies often washed ashore and collected for burial |
—
|
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: bodies often washed ashore and collected for burial | Statement: [Wallabout Bay burial pits, conditionOfBurials, bodies often washed ashore and collected for burial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionOfBurials Context triple: [Wallabout Bay burial pits, conditionOfBurials, bodies often washed ashore and collected for burial]
-
A.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
-
B.
burialDetail
chosen
Indicates details about how, where, and under what circumstances an entity is buried.
-
C.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
D.
periodOfBurial
Indicates the time period or date range during which the burial of an entity took place.
-
E.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7209404788190b82e108a25baa39e |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.