Triple
T8249699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsieur G—— |
E192925
|
entity |
| Predicate | offersRewardFor |
P81187
|
FINISHED |
| Object | recovery of the purloined letter |
—
|
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: recovery of the purloined letter | Statement: [Monsieur G——, offersRewardFor, recovery of the purloined letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersRewardFor Context triple: [Monsieur G——, offersRewardFor, recovery of the purloined letter]
-
A.
offeredRewardTo
Indicates that one entity has proposed or promised a reward to another entity, typically as an incentive for a specific action or outcome.
-
B.
offersAward
Indicates that one entity grants or makes available an award or prize to another entity.
-
C.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
-
D.
grantedAsRewardFor
Indicates that something is given to an entity specifically as a reward for a particular action, achievement, or service.
-
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. chosen
Provenance (4 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78c817708190ad1c364e12083d26 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb44d1caa881909069fa925a91316b |
completed | March 31, 2026, 3:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.