Triple
T25457837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hauptmann von Köpenick affair |
E637960
|
entity |
| Predicate | amountStolen |
P124858
|
FINISHED |
| Object | about 4000 marks |
—
|
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: about 4000 marks | Statement: [Hauptmann von Köpenick affair, amountStolen, about 4000 marks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amountStolen Context triple: [Hauptmann von Köpenick affair, amountStolen, about 4000 marks]
-
A.
approximateValueStolenInUSDAtTheTime
Indicates the estimated amount of money, in U.S. dollars and valued at the time of the theft, that was stolen in the described incident.
-
B.
amountInvolvedApprox
chosen
Indicates that the relationship specifies an approximate value or quantity involved in an action, event, or transaction.
-
C.
approximateValueStolenInEther
Indicates the estimated amount of value stolen, expressed in units of Ether.
-
D.
numberOfWorksStolen
Indicates the quantity of works that have been taken unlawfully from a particular source or owner.
-
E.
stolenBy
Indicates that something has been taken unlawfully or without permission by a particular entity.
- 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_69f5f72884408190b586de6cd827e1d4 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:10 p.m.