Triple
T31520314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fasolt |
E804188
|
entity |
| Predicate | receivesAsRansom |
P177586
|
FINISHED |
| Object | Rhinegold treasure |
—
|
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: Rhinegold treasure | Statement: [Fasolt, receivesAsRansom, Rhinegold treasure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesAsRansom Context triple: [Fasolt, receivesAsRansom, Rhinegold treasure]
-
A.
ransom
Indicates demanding payment or concessions in exchange for releasing a person, object, or information held under threat or coercion.
-
B.
ransomOfferedBy
Indicates that a ransom has been proposed or promised by one party in exchange for the release, return, or safety of another party or asset.
-
C.
ransomPaid
Indicates that a payment has been made to secure the release of a person, property, or information held under threat or coercion.
-
D.
blackmailedThrough
Indicates a coercive relationship where one party forces another to act or comply by threatening to reveal damaging or compromising information through a specific intermediary or channel.
-
E.
blackmailedFor
Indicates that one entity coerces another into doing or not doing something by threatening to reveal damaging or sensitive information about them.
- F. None of above. chosen
Provenance (4 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 30, 2026, 9:55 p.m.