Triple
T30579737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdul Rahman Yasin |
E778348
|
entity |
| Predicate | rewardOfferedBy |
P169870
|
FINISHED |
| Object | United States government |
—
|
NE NERFINISHED |
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: United States government | Statement: [Abdul Rahman Yasin, rewardOfferedBy, United States government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardOfferedBy Context triple: [Abdul Rahman Yasin, rewardOfferedBy, United States government]
-
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.
offersRewardFor
Indicates that one entity promises or provides a reward in exchange for another entity performing a specified action or achieving a particular outcome.
-
C.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
D.
offersAward
Indicates that one entity grants or makes available an award or prize to another entity.
-
E.
offeringOutcome
Indicates the result or consequence that follows from making a particular offering.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6894176d0819096fe66b9baab66f1 |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:23 p.m.