Triple
T22328920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolbeault cohomology class |
E551971
|
entity |
| Predicate | zeroClassCondition |
P9150
|
FINISHED |
| Object | form is ∂̄-exact |
—
|
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: form is ∂̄-exact | Statement: [Dolbeault cohomology class, zeroClassCondition, form is ∂̄-exact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zeroClassCondition Context triple: [Dolbeault cohomology class, zeroClassCondition, form is ∂̄-exact]
-
A.
conditionOnZeros
Indicates that one entity’s state, behavior, or validity depends specifically on the presence, position, or pattern of zero values in another entity.
-
B.
zeroDefinition
Indicates that something has no defined value, quantity, or specification within the given context.
-
C.
isZeroFor
chosen
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
-
D.
dropCondition
Indicates that an entity ceases to satisfy, or is no longer subject to, a specified condition or requirement.
-
E.
remainderCondition
Indicates that a specified remainder-based condition (such as a modulo constraint) holds between one or more values.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1576ab52c819087563cd778d6bc5e |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.