Triple
T26286758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McL |
E661158
|
entity |
| Predicate | schurMultiplierOrder |
P77146
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [McL, schurMultiplierOrder, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schurMultiplierOrder Context triple: [McL, schurMultiplierOrder, 3]
-
A.
hasSchurMultiplierOrder
chosen
Indicates the relationship that specifies the order (size) of the Schur multiplier associated with a given group or algebraic structure.
-
B.
automorphismGroupOrder
Indicates the size of the group of all structure-preserving bijections (automorphisms) of an object under composition.
-
C.
multiplicativeGroupOrder
Indicates the size (number of elements) of the multiplicative group associated with a given structure or modulus.
-
D.
hasSymmetryGroupOrder
Indicates that an entity possesses a symmetry group whose total number of distinct symmetry operations equals the given order.
-
E.
hasOuterAutomorphismGroupOrder
Indicates the relationship that specifies the order (size) of the outer automorphism group associated with a given mathematical structure.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e781b108190b5479e4992d58695 |
completed | May 2, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:05 p.m.