Triple
T37172728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish Community of Trondheim |
E920957
|
entity |
| Predicate | subjectToEvent |
P177130
|
FINISHED |
| Object | Holocaust in Norway |
—
|
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: Holocaust in Norway | Statement: [Jewish Community of Trondheim, subjectToEvent, Holocaust in Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToEvent Context triple: [Jewish Community of Trondheim, subjectToEvent, Holocaust in Norway]
-
A.
subjectOfEvent
chosen
Indicates that an entity participates in or is involved in a particular event as one of its primary actors or focal points.
-
B.
impliesEvent
Indicates that one event logically leads to, entails, or guarantees the occurrence of another event.
-
C.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
-
D.
enabledEvent
Indicates that one entity has activated or allowed a particular event to occur or be triggered.
-
E.
selectedEvent
Indicates that a particular event has been chosen or designated from a set of possible events.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.