Triple
T23244617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Proetus |
E581550
|
entity |
| Predicate | rewardToMelampus |
P25342
|
FINISHED |
| Object | part of his kingdom |
—
|
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: part of his kingdom | Statement: [King Proetus, rewardToMelampus, part of his kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardToMelampus Context triple: [King Proetus, rewardToMelampus, part of his kingdom]
-
A.
monetaryReward
Indicates that one entity provides or promises a payment of money to another as compensation, incentive, or prize.
-
B.
rewardFulfilledFor
chosen
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
-
C.
rewardSignal
Indicates that one entity provides a signal representing feedback or incentive (such as a reward or penalty) to guide another entity’s behavior or learning process.
-
D.
rewardMechanism
Indicates a relationship where an entity provides or defines a system of incentives or compensation in response to certain actions, behaviors, or outcomes.
-
E.
rewardInHereafter
Indicates that an action or state results in a positive recompense or benefit granted in the afterlife.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.