Triple
T26191727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | q-Onsager algebra |
E654981
|
entity |
| Predicate | hasDefiningGenerators |
P78098
|
FINISHED |
| Object | two generators A0 and A1 |
—
|
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: two generators A0 and A1 | Statement: [q-Onsager algebra, hasDefiningGenerators, two generators A0 and A1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefiningGenerators Context triple: [q-Onsager algebra, hasDefiningGenerators, two generators A0 and A1]
-
A.
hasGeneratingFunction
Indicates that one entity serves as the generating function associated with, or defining, another entity.
-
B.
hasGeneratorType
Indicates that an entity is associated with or uses a specific type or category of generator.
-
C.
isGeneratorWith
Indicates that one entity functions as a generator that is associated with, configured for, or used in conjunction with another entity.
-
D.
hasGeneratorDegrees
Indicates that an entity possesses one or more generator units characterized by specific degree values or ratings.
-
E.
hasStandardGenerators
chosen
Indicates that an entity possesses a designated or commonly accepted set of generators that define or produce it according to a standard.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 26, 2026, 8:44 p.m.