Triple
T7871627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobi triple product |
E182749
|
entity |
| Predicate | conditionOnq |
P61769
|
FINISHED |
| Object | |q| < 1 |
—
|
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: |q| < 1 | Statement: [Jacobi triple product, conditionOnq, |q| < 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionOnq Context triple: [Jacobi triple product, conditionOnq, |q| < 1]
-
A.
holdsUnderCondition
chosen
Indicates that one fact, rule, or relationship remains valid only when a specified condition or set of conditions is satisfied.
-
B.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
C.
contingentOn
Indicates that the occurrence, validity, or outcome of one event or condition depends on the fulfillment or existence of another.
-
D.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
-
E.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
- 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.