Triple
T21151652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aricie |
E521205
|
entity |
| Predicate | rewardAtEndOfWork |
P108785
|
FINISHED |
| Object | union with Hippolyte |
—
|
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: union with Hippolyte | Statement: [Aricie, rewardAtEndOfWork, union with Hippolyte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardAtEndOfWork Context triple: [Aricie, rewardAtEndOfWork, union with Hippolyte]
-
A.
rewardForCompletion
chosen
Indicates that something is given as a benefit or compensation in return for successfully completing a task, activity, or objective.
-
B.
rewardFulfilledFor
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
-
C.
rewardInHereafter
Indicates that an action or state results in a positive recompense or benefit granted in the afterlife.
-
D.
rewardUnit
Indicates that one entity serves as the unit or measure in which a reward is quantified or granted to another entity.
-
E.
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.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72401830c8190a2008c40c4174d97 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.