Triple
T20690768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rozansky–Witten theory |
E508542
|
entity |
| Predicate | quantizationType |
P141098
|
FINISHED |
| Object | topological |
—
|
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: topological | Statement: [Rozansky–Witten theory, quantizationType, topological]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quantizationType Context triple: [Rozansky–Witten theory, quantizationType, topological]
-
A.
quantizationIs
Indicates that one entity is a specific quantization or discretized representation of another entity.
-
B.
isQuantizationOf
Indicates that one entity is a quantized or discretized version of another, typically transforming a continuous model, signal, or system into a discrete counterpart.
-
C.
isQuantizedBy
Indicates that a continuous or variable quantity is represented or constrained using discrete units, levels, or steps defined by another entity.
-
D.
supportsQuantization
Indicates that one entity is capable of operating with, or is compatible with, quantized representations or computations of another entity.
-
E.
usedToQuantize
Indicates that one entity serves as the quantization method, scheme, or tool applied to another entity.
- F. None of above. chosen
Provenance (4 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10d83548190a52b9ef84c8f9205 |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:08 p.m.