Triple
T2471110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindbergh kidnapping |
E55374
|
entity |
| Predicate | ransomCurrency |
P11731
|
FINISHED |
| Object | gold certificates |
—
|
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: gold certificates | Statement: [Lindbergh kidnapping, ransomCurrency, gold certificates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ransomCurrency Context triple: [Lindbergh kidnapping, ransomCurrency, gold certificates]
-
A.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
B.
currencyType
chosen
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
C.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
-
D.
currencyOfDenomination
Indicates that one currency unit is a specific denomination or face value within another currency system.
-
E.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
- 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.