Triple
T26254887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | monstrous moonshine |
E656689
|
entity |
| Predicate | awardRelated |
P11
|
FINISHED |
| Object | Borcherds Fields Medal 1998 |
—
|
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: Borcherds Fields Medal 1998 | Statement: [monstrous moonshine, awardRelated, Borcherds Fields Medal 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardRelated Context triple: [monstrous moonshine, awardRelated, Borcherds Fields Medal 1998]
-
A.
awardConferred
Indicates that an award or honor has been formally granted by one entity to another.
-
B.
awardReceived
chosen
Indicates that an entity has been granted or honored with a specific award or recognition.
-
C.
relatedAward
Indicates that there is an award connected or associated with the subject entity, such as an honor, prize, or recognition related to it.
-
D.
awardRelatedWork
Indicates that there is a connection between an award and the work (such as a project, publication, or performance) for which it was given or with which it is associated.
-
E.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 26, 2026, 9:08 p.m.