Triple
T26255028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(2,ℤ) |
E656692
|
entity |
| Predicate | fundamentalIn |
P4501
|
FINISHED |
| Object | theory of modular forms |
—
|
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: theory of modular forms | Statement: [SL(2,ℤ), fundamentalIn, theory of modular forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundamentalIn Context triple: [SL(2,ℤ), fundamentalIn, theory of modular forms]
-
A.
isFundamental
Indicates that something is a basic, essential, or foundational element upon which other things depend or are built.
-
B.
foundation
Indicates that one entity serves as the base, support, or underlying basis upon which another entity is built, established, or depends.
-
C.
underpins
Indicates that one entity serves as the fundamental basis, support, or justification for another.
-
D.
underlies
chosen
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
-
E.
founds
Indicates that an entity establishes or creates an organization, institution, settlement, or similar entity, typically as its originator.
- 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_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:08 p.m.