Triple
T6062538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ringelblum Archive |
E135066
|
entity |
| Predicate | inscribedOnUNESCORegister |
P57323
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Ringelblum Archive, inscribedOnUNESCORegister, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscribedOnUNESCORegister Context triple: [Ringelblum Archive, inscribedOnUNESCORegister, 1999]
-
A.
inscribedOnUNESCOListInYear
chosen
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
-
B.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
-
C.
UNESCOHeritage
Indicates that a place, site, or cultural/natural asset has been officially inscribed on the UNESCO World Heritage List as having outstanding universal value.
-
D.
UNESCOWorldHeritageSiteWithin
Indicates that a UNESCO World Heritage Site is geographically located within the boundaries of a specified area or region.
-
E.
UNESCOSessionOfInscription
Indicates the specific UNESCO session during which an item was formally inscribed or added to a UNESCO list.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0572100e8819084c3174921a2d527 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.