Triple
T31490216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nibelung hoard |
E803385
|
entity |
| Predicate | usedAsRansomFor |
P177586
|
FINISHED |
| Object | Freia |
—
|
NE NERFINISHED |
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: Freia | Statement: [Nibelung hoard, usedAsRansomFor, Freia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsRansomFor Context triple: [Nibelung hoard, usedAsRansomFor, Freia]
-
A.
receivesAsRansom
chosen
Indicates that one entity accepts another entity as payment or exchange in a ransom situation.
-
B.
ransom
Indicates demanding payment or concessions in exchange for releasing a person, object, or information held under threat or coercion.
-
C.
isExploitedFor
Indicates that one entity is unfairly or abusively used by another entity as a resource, means, or advantage for the latter’s benefit.
-
D.
exploitedFor
Indicates that one entity is unfairly or abusively used by another entity as a resource, means, or advantage for the latter’s benefit.
-
E.
ransomPaid
Indicates that a payment has been made to secure the release of a person, property, or information held under threat or coercion.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 30, 2026, 9:37 p.m.