Triple
T6311894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emanuel Ringelblum |
E141521
|
entity |
| Predicate | archiveBuriedIn |
P69990
|
FINISHED |
| Object | milk cans in Warsaw Ghetto |
—
|
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: milk cans in Warsaw Ghetto | Statement: [Emanuel Ringelblum, archiveBuriedIn, milk cans in Warsaw Ghetto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archiveBuriedIn Context triple: [Emanuel Ringelblum, archiveBuriedIn, milk cans in Warsaw Ghetto]
-
A.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
B.
buriedFor
Indicates that one entity is buried on behalf of, in honor of, or as a memorial for another entity.
-
C.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
D.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
E.
archivesType
Indicates that one entity serves as an archival record or stored version of another entity, specifying the type or category of that archived content.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0649d1e048190a3fc7fbce9d2ee57 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:28 p.m.