Triple
T28520746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Twelve Dancing Princesses |
E721756
|
entity |
| Predicate | rewardForHero |
P120108
|
FINISHED |
| Object | marriage to one of the princesses |
—
|
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: marriage to one of the princesses | Statement: [The Twelve Dancing Princesses, rewardForHero, marriage to one of the princesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardForHero Context triple: [The Twelve Dancing Princesses, rewardForHero, marriage to one of the princesses]
-
A.
rewardForCharacters
chosen
Indicates that a reward is given in recognition of the actions, qualities, or roles of specific characters.
-
B.
rewardForCompletion
Indicates that something is given as a benefit or compensation in return for successfully completing a task, activity, or objective.
-
C.
monetaryReward
Indicates that one entity provides or promises a payment of money to another as compensation, incentive, or prize.
-
D.
rewardInHereafter
Indicates that an action or state results in a positive recompense or benefit granted in the afterlife.
-
E.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fa24a6481908c8b6651cbaf0664 |
completed | May 2, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:20 a.m.