Triple
T26254869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | monstrous moonshine |
E656689
|
entity |
| Predicate | conjectureDate |
P38260
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [monstrous moonshine, conjectureDate, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conjectureDate Context triple: [monstrous moonshine, conjectureDate, 1970s]
-
A.
conjecturedSign
Indicates that one entity is proposed or hypothesized to be the sign, symbol, or indicator of another entity, without confirmed certainty.
-
B.
associatedConjecture
chosen
Indicates that one entity is linked or connected to a particular conjecture, typically as its subject, source, or relevant context.
-
C.
refinedConjecture
Indicates that a previously stated conjecture has been modified or made more precise, resulting in a refined version of the original conjecture.
-
D.
relatedConjecture
Indicates that one conjecture is connected or associated with another conjecture, such as by similarity, dependency, or thematic relation.
-
E.
historicalConjectureBy
Indicates that a historical conjecture, theory, or speculative claim is proposed or formulated by a particular agent or source.
- 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_69f60dcd2e688190b54e36b0ff0d9187 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:08 p.m.