Triple
T5212158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weyl algebra |
E117658
|
entity |
| Predicate | satisfiesRelation |
P4233
|
FINISHED |
| Object | p x - x p = 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: p x - x p = 1 | Statement: [Weyl algebra, satisfiesRelation, p x - x p = 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satisfiesRelation Context triple: [Weyl algebra, satisfiesRelation, p x - x p = 1]
-
A.
satisfies
chosen
Indicates that one entity meets, fulfills, or complies with the requirements, conditions, or expectations specified by another.
-
B.
supportsRelation
Indicates that one entity provides assistance, endorsement, or structural backing to another entity or its activity.
-
C.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
D.
representsInRelationsWith
Indicates that an entity serves as a representative or proxy for another entity within a specified relationship or set of relationships.
-
E.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
- 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_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. |
Created at: March 20, 2026, 1:47 p.m.