Triple
T30181511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Vice-Consul in Budapest |
E767211
|
entity |
| Predicate | aimOfActions |
P64674
|
FINISHED |
| Object | prevent deportation of Jews |
—
|
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: prevent deportation of Jews | Statement: [Swiss Vice-Consul in Budapest, aimOfActions, prevent deportation of Jews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfActions Context triple: [Swiss Vice-Consul in Budapest, aimOfActions, prevent deportation of Jews]
-
A.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
C.
goalDescription
Indicates that an entity expresses, specifies, or provides a textual description of a goal or intended outcome associated with another entity or activity.
-
D.
semanticGoal
Indicates that an entity has a target meaning or intended semantic outcome it aims to achieve or convey.
-
E.
actorObjective
Indicates that an actor has a specific goal, purpose, or intended outcome in relation to another entity or situation.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f419e088190ba19a6ab9465d951 |
completed | May 2, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:26 p.m.