Triple
T34161894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bölverk |
E876299
|
entity |
| Predicate | bargainsWith |
P178461
|
FINISHED |
| Object | Baugi |
—
|
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: Baugi | Statement: [Bölverk, bargainsWith, Baugi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bargainsWith Context triple: [Bölverk, bargainsWith, Baugi]
-
A.
bargainsFor
Indicates that one entity negotiates or seeks to obtain another entity, typically aiming for more favorable terms or conditions.
-
B.
conditionOfBargain
Indicates that one entity is a term, stipulation, or requirement that forms part of the agreed exchange in a bargain or contract.
-
C.
offersDiscountsOn
Indicates that one entity provides price reductions or special discount deals specifically applied to another entity or its associated items or services.
-
D.
offeredBundle
Indicates that one entity has presented a specific combination of items or services together as a bundled offer to another entity.
-
E.
PaulOffers
Indicates that Paul presents or proposes something (such as help, goods, or an opportunity) to another party for their consideration or acceptance.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:54 a.m.