Triple
T33996290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust in Italy |
E871680
|
entity |
| Predicate | memoryInstitution |
P49721
|
FINISHED |
| Object | Memoriale della Shoah di Milano |
—
|
NE NERFINISHED |
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: Memoriale della Shoah di Milano | Statement: [Holocaust in Italy, memoryInstitution, Memoriale della Shoah di Milano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memoryInstitution Context triple: [Holocaust in Italy, memoryInstitution, Memoriale della Shoah di Milano]
-
A.
inInstitution
chosen
Indicates that an entity is located within, belongs to, or is formally associated with a particular institution.
-
B.
trainingInstitution
Indicates that one entity serves as the institution or organization where another entity receives training or education.
-
C.
commonInstitution
Indicates that two or more entities share affiliation with the same institution (such as an organization, school, or company).
-
D.
institutes
Indicates that an entity establishes, initiates, or formally sets up another entity, process, or system.
-
E.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f72ad38a208190b4bdc828297f86ad |
completed | May 3, 2026, 11 a.m. |
| PD | Predicate disambiguation | batch_69f72a0243988190a43b8ea22457cd30 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 1:50 a.m.