Triple
T2408418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klein quartic |
E50328
|
entity |
| Predicate | hasSpecialRoleIn |
P27764
|
FINISHED |
| Object | theory of Riemann surfaces |
—
|
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 Riemann surfaces | Statement: [Klein quartic, hasSpecialRoleIn, theory of Riemann surfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialRoleIn Context triple: [Klein quartic, hasSpecialRoleIn, theory of Riemann surfaces]
-
A.
hasNotableRoleIn
chosen
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
B.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
C.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
D.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
E.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
- 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abceab9ce881909ae0a2f34515c11e |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5a530e8819094105aa92dfaf6b3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:58 p.m.