Triple
T7871658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobi triple product |
E182749
|
entity |
| Predicate | isClassicalResult |
P74560
|
FINISHED |
| Object | 19th-century mathematics |
—
|
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: 19th-century mathematics | Statement: [Jacobi triple product, isClassicalResult, 19th-century mathematics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClassicalResult Context triple: [Jacobi triple product, isClassicalResult, 19th-century mathematics]
-
A.
hasClassicResult
chosen
Indicates that an entity is associated with a canonical, established, or traditionally recognized result or outcome.
-
B.
numberInClassicalTradition
Indicates that an entity is associated with a specific number as defined or used within a particular classical tradition (e.g., mythology, religion, or philosophy).
-
C.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
D.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
E.
knownResult
Indicates that the outcome or consequence of an action, process, or event is already determined and available.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39a5950481908399211c5dfe2569 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:56 p.m.