Triple
T33478927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discover Book of the Year |
E857407
|
entity |
| Predicate | benefitToWinners |
P487
|
FINISHED |
| Object | increased visibility |
—
|
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: increased visibility | Statement: [Discover Book of the Year, benefitToWinners, increased visibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitToWinners Context triple: [Discover Book of the Year, benefitToWinners, increased visibility]
-
A.
beneficiaries
Indicates that certain entities receive advantages, profits, or positive outcomes from an action, event, or arrangement.
-
B.
benefits
chosen
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
C.
benefitEvent
Indicates that an event is organized primarily to provide a benefit, such as raising funds or support, for a particular cause, group, or individual.
-
D.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
E.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:38 a.m.