Triple
T38297832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur C. Cope |
E1032139
|
entity |
| Predicate | awardNamedInHonorOf |
P130939
|
FINISHED |
| Object | Arthur C. Cope Award |
—
|
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: Arthur C. Cope Award | Statement: [Arthur C. Cope, awardNamedInHonorOf, Arthur C. Cope Award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardNamedInHonorOf Context triple: [Arthur C. Cope, awardNamedInHonorOf, Arthur C. Cope Award]
-
A.
awardEstablishedInHisHonorBy
Indicates that an award was created in honor of a specific person by a particular individual or organization.
-
B.
namedInHonorBy
Indicates that one entity has been used as the namesake or dedicatee by another entity, signifying that the latter is named in honor of the former.
-
C.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
D.
awardTo
Indicates that an award, prize, or honor is given or assigned to a particular recipient.
-
E.
namedAwardAfter
chosen
Indicates that an award has been given a name in honor of or derived from a particular person, group, or 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.