Triple
T37546986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COPSS Award |
E933489
|
entity |
| Predicate | typicalAwardeeRole |
P43861
|
FINISHED |
| Object | academic statistician |
—
|
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: academic statistician | Statement: [COPSS Award, typicalAwardeeRole, academic statistician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAwardeeRole Context triple: [COPSS Award, typicalAwardeeRole, academic statistician]
-
A.
honoreeRole
chosen
Indicates the specific role, title, or capacity in which an individual is being honored in relation to an award, event, or recognition.
-
B.
typicalLaureateType
Indicates the usual or most common type or category of laureate associated with something.
-
C.
typicalAwardedBy
Indicates the usual or standard agent (such as a person or organization) that confers or grants a particular award.
-
D.
typicalAdditionalRole
Indicates that an entity commonly or characteristically holds an extra role or function in addition to its primary one.
-
E.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.