Triple
T31419534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sürgün |
E801491
|
entity |
| Predicate | reasonGivenByAuthorities |
P24494
|
FINISHED |
| Object | alleged collaboration with Nazi Germany |
—
|
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: alleged collaboration with Nazi Germany | Statement: [Sürgün, reasonGivenByAuthorities, alleged collaboration with Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonGivenByAuthorities Context triple: [Sürgün, reasonGivenByAuthorities, alleged collaboration with Nazi Germany]
-
A.
reasonForGrant
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
-
B.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
C.
reasonForJudgment
Indicates that a particular reason, basis, or justification underlies or explains a given judgment or decision.
-
D.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
E.
reasonForConviction
Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 30, 2026, 8:46 p.m.