Triple
T22260697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Learned Hand Medal for Excellence in Federal Jurisprudence |
E550214
|
entity |
| Predicate | namedAfterPersonRole |
P117536
|
FINISHED |
| Object | jurist |
—
|
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: jurist | Statement: [Learned Hand Medal for Excellence in Federal Jurisprudence, namedAfterPersonRole, jurist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterPersonRole Context triple: [Learned Hand Medal for Excellence in Federal Jurisprudence, namedAfterPersonRole, jurist]
-
A.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
B.
namedAfterOccupationOrRole
chosen
Indicates that an entity is named after a specific occupation, profession, or social role associated with a person or group.
-
C.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
D.
hasNamesakeRoleFor
Indicates that one entity holds a role or position that is named after, or serves as a namesake for, another entity.
-
E.
hasNamedAfterPerson
Indicates that one entity is named in honor of, or derived from the name of, a specific person.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141b703b081909a2b432463a8e2df |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.