Triple
T5212170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | first Weyl algebra A1(k) |
E117658
|
entity |
| Predicate | hasPresentation |
P62047
|
FINISHED |
| Object | k⟨x,∂⟩/(∂x - x∂ - 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: k⟨x,∂⟩/(∂x - x∂ - 1) | Statement: [first Weyl algebra A1(k), hasPresentation, k⟨x,∂⟩/(∂x - x∂ - 1)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPresentation Context triple: [first Weyl algebra A1(k), hasPresentation, k⟨x,∂⟩/(∂x - x∂ - 1)]
-
A.
hasPresented
Indicates that one entity has formally given, delivered, or shown something (such as information, a work, or an award) to another entity.
-
B.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
C.
presentedFor
Indicates that one entity was formally offered, submitted, or shown to another entity for consideration, review, or action.
-
D.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
-
E.
presentedIn
Indicates that something is shown, displayed, or formally introduced within a particular context, medium, event, or setting.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a730e6c8190ae6082da41ee592a |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79000cf88190b3c05d95395b0cd2 |
completed | March 20, 2026, 4:42 p.m. |
Created at: March 20, 2026, 1:47 p.m.