Triple
T21046979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | orthogonal group O(n) |
E518473
|
entity |
| Predicate | isFiniteFor |
P9155
|
FINISHED |
| Object | no positive integer n |
—
|
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: no positive integer n | Statement: [orthogonal group O(n), isFiniteFor, no positive integer n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFiniteFor Context triple: [orthogonal group O(n), isFiniteFor, no positive integer n]
-
A.
isFinite
Indicates that the value, set, or quantity in question is limited in size or extent and does not continue indefinitely.
-
B.
isInfinite
Indicates that something has no finite limit, bound, or endpoint in size, extent, or duration.
-
C.
finiteAt
chosen
Indicates that a function, quantity, or value remains finite (not infinite or undefined) at a specified point or under a given condition.
-
D.
usesFiniteField
Indicates that one entity employs or operates within a finite field as part of its structure, computation, or definition.
-
E.
hasFiniteSupport
Indicates that a function, relation, or structure is nonzero or nontrivial at only finitely many elements of its domain.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf4d26481908b639996500a8319 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.