Triple
T19273617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mammo |
E481989
|
entity |
| Predicate | acclaimedFor |
P135397
|
FINISHED |
| Object | sensitive portrayal of Partition’s human impact |
—
|
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: sensitive portrayal of Partition’s human impact | Statement: [Mammo, acclaimedFor, sensitive portrayal of Partition’s human impact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acclaimedFor Context triple: [Mammo, acclaimedFor, sensitive portrayal of Partition’s human impact]
-
A.
alsoAwardedIn
Indicates that the same award or recognition was given in an additional time, place, or context beyond the primary one.
-
B.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
C.
notableAwardedFor
Indicates that an award is notable specifically for being given in recognition of a particular work, achievement, or contribution.
-
D.
celebratedAs
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
E.
notableAwardWon
Indicates that an entity has received a specific notable award as a winner.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbba7758819081c1c78667c59c5e |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:29 p.m.