Triple
T20690757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rozansky–Witten theory |
E508542
|
entity |
| Predicate | targetSpace |
P141097
|
FINISHED |
| Object | hyperkähler manifold |
—
|
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: hyperkähler manifold | Statement: [Rozansky–Witten theory, targetSpace, hyperkähler manifold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetSpace Context triple: [Rozansky–Witten theory, targetSpace, hyperkähler manifold]
-
A.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
targetArea
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
C.
targetLocation
Indicates the specific place or destination toward which an action, movement, or effect is directed.
-
D.
pace
Indicates the rate or speed at which an action, process, or sequence progresses over time.
-
E.
targetUnit
Indicates that one entity serves as the specific unit or object that another entity is directed at, operates on, or is intended to affect.
- 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.