Triple
T35035211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert W. Bingham Prize |
E1010891
|
entity |
| Predicate | eligibleAuthorType |
P56172
|
FINISHED |
| Object | debut author |
—
|
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: debut author | Statement: [Robert W. Bingham Prize, eligibleAuthorType, debut author]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleAuthorType Context triple: [Robert W. Bingham Prize, eligibleAuthorType, debut author]
-
A.
eligibleAuthors
Indicates that certain authors meet the required conditions or criteria to qualify for a specified role, status, or action.
-
B.
hasAuthorType
chosen
Indicates that an entity is associated with an author characterized by a specific role, category, or type.
-
C.
eligiblePersons
Indicates that certain persons meet the required conditions or criteria to qualify for a particular status, benefit, or participation.
-
D.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
E.
eligibleEntityType
Indicates that an entity is of a type that qualifies it to participate in or be subject to a specified rule, process, or condition.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.