Triple
T15758653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muranów district |
E382034
|
entity |
| Predicate | hasMemorialTheme |
P53946
|
FINISHED |
| Object | Jewish resistance |
—
|
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: Jewish resistance | Statement: [Muranów district, hasMemorialTheme, Jewish resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemorialTheme Context triple: [Muranów district, hasMemorialTheme, Jewish resistance]
-
A.
memorialTheme
chosen
Indicates that something (such as a work, event, or object) is dedicated to remembering, honoring, or commemorating a person, group, or event.
-
B.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
C.
hasMemorialContext
Indicates that something is related to, associated with, or situated within the context of a memorial or commemorative setting.
-
D.
hasMemorialRoom
Indicates that an entity possesses or contains a dedicated room serving as a memorial to a person, group, or event.
-
E.
hasMemorialPractice
Indicates that an entity engages in or is associated with a particular practice, ritual, or activity intended to commemorate or remember someone or something.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b35ea48190a758ee76a57b5451 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.