Triple
T21046843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sperner family |
E518470
|
entity |
| Predicate | maximalityConcept |
P142615
|
FINISHED |
| Object | maximal Sperner family |
—
|
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: maximal Sperner family | Statement: [Sperner family, maximalityConcept, maximal Sperner family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximalityConcept Context triple: [Sperner family, maximalityConcept, maximal Sperner family]
-
A.
maxim
Indicates a general principle or rule that guides or characterizes an entity’s behavior, decisions, or actions.
-
B.
definesMaximum
Indicates that one entity specifies or sets the upper limit or greatest allowable value for another entity.
-
C.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
-
D.
maximalIdealsCorrespondTo
Indicates that there is a correspondence or bijective relationship between maximal ideals in one structure and certain objects or properties in another structure.
-
E.
maximumCeiling
Indicates the highest allowable or achievable limit or value that something cannot exceed.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:34 p.m.