Triple
T15918588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Szekeres configuration |
E386033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combinatorial configuration |
C29195
|
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: combinatorial configuration Context triple: [Szekeres configuration, instanceOf, combinatorial configuration]
-
A.
symmetric block design
A symmetric block design is a combinatorial design in which the number of points equals the number of blocks, and each pair of distinct points occurs together in the same number of blocks.
-
B.
(7,3,1)-design
A (7,3,1)-design is a combinatorial incidence structure consisting of 7 points and 7 three-point blocks such that every pair of distinct points lies together in exactly one block.
-
C.
projective plane of order 2
chosen
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).
-
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.
combinatorial basis
A combinatorial basis is a minimal set of combinatorial objects or elements from which all structures in a given class can be uniquely generated or represented, typically without redundancy.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.