Triple

T25457832
Position Surface form Disambiguated ID Type / Status
Subject Hauptmann von Köpenick affair E637960 entity
Predicate involvedImpersonationOf P20150 FINISHED
Object Prussian army officer 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: Prussian army officer | Statement: [Hauptmann von Köpenick affair, involvedImpersonationOf, Prussian army officer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: involvedImpersonationOf
Context triple: [Hauptmann von Köpenick affair, involvedImpersonationOf, Prussian army officer]
  • A. allegedImpostor
    Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
  • B. disguisedAs chosen
    Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
  • C. actsOnBehalfOf
    Indicates that one entity performs actions or makes decisions as a representative or proxy for another entity.
  • D. actsInSteadOf
    Indicates that one entity performs an action or fulfills a role as a substitute or proxy for another entity.
  • E. intrudedInto
    Indicates that one entity has entered or encroached upon another entity’s space, domain, or context without permission or in an unwelcome manner.
  • 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_69e75db8bab08190baca80b4a8c315fd completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f674e06c9481909ed0ea736408f0d7 completed May 2, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69f673c2f81c8190bf369226306eef09 completed May 2, 2026, 9:59 p.m.
Created at: April 21, 2026, 2:10 p.m.