Triple
T31217936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar Dadon |
E795922
|
entity |
| Predicate | grantsRewardPromiseTo |
P81187
|
FINISHED |
| Object | the astrologer |
—
|
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: the astrologer | Statement: [Tsar Dadon, grantsRewardPromiseTo, the astrologer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsRewardPromiseTo Context triple: [Tsar Dadon, grantsRewardPromiseTo, the astrologer]
-
A.
grantedAsRewardFor
Indicates that something is given to an entity specifically as a reward for a particular action, achievement, or service.
-
B.
believedToGrant
Indicates that something is thought or assumed to provide, confer, or bestow a particular benefit, quality, or effect.
-
C.
offersRewardFor
chosen
Indicates that one entity promises or provides a reward in exchange for another entity performing a specified action or achieving a particular outcome.
-
D.
aimedToGrant
Indicates an intention or effort to provide or confer something (such as a right, benefit, or permission) to a recipient.
-
E.
grantsRecognitionTo
Indicates that one entity formally acknowledges, honors, or validates another entity’s achievements, status, or contributions.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 9:10 p.m.