Triple
T34419275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serre’s theorem on projective embeddings via ample line bundles |
E883482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in projective geometry |
C10469
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: result in projective geometry Context triple: [Serre’s theorem on projective embeddings via ample line bundles, instanceOf, result in projective geometry]
-
A.
configuration in projective geometry
A configuration in projective geometry is a structured arrangement of points, lines, and sometimes higher-dimensional subspaces, together with specified incidence relations among them.
-
B.
projective plane of order 2
A projective plane of order 2 is a finite incidence structure with 7 points and 7 lines where each line contains 3 points, each point lies on 3 lines, and any two distinct points (or lines) determine a unique line (or point).
-
C.
result in geometry
chosen
A result in geometry is a proven statement or theorem that describes a specific property, relationship, or behavior of geometric figures and spaces.
-
D.
finite projective plane
A finite projective plane is a finite incidence structure of points and lines in which any two distinct points lie on a unique common line, any two distinct lines meet in a unique common point, and there exist four points no three of which are collinear.
-
E.
projective linear group
The projective linear group is the group of invertible linear transformations of a vector space modulo scalar multiples, equivalently the group of automorphisms of a projective space induced by linear maps.
- F. None of above.
Provenance (1 batch)
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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2 a.m.