Triple
T36593217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. twenty-dollar bill (planned redesign) |
E902724
|
entity |
| Predicate | personHonored |
P51704
|
FINISHED |
| Object | Harriet Tubman |
—
|
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: Harriet Tubman | Statement: [U.S. twenty-dollar bill (planned redesign), personHonored, Harriet Tubman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personHonored Context triple: [U.S. twenty-dollar bill (planned redesign), personHonored, Harriet Tubman]
-
A.
honoredPerson
chosen
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
B.
honorsPerson
Indicates that one entity formally recognizes, respects, or pays tribute to a specific person.
-
C.
honoreeRole
Indicates the specific role, title, or capacity in which an individual is being honored in relation to an award, event, or recognition.
-
D.
artistHonored
Indicates that one entity has been formally recognized or celebrated in honor of an artist.
-
E.
typicalHonoree
Indicates that an entity is the usual or characteristic recipient of an honor, award, or recognition associated with 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.