Triple
T24806936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson solids |
E620679
|
entity |
| Predicate | areConvex |
P157344
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Johnson solids, areConvex, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areConvex Context triple: [Johnson solids, areConvex, true]
-
A.
isConcaveIn
Indicates that a function or relation curves inward (is concave) with respect to a specified variable or argument, so that any line segment between two points on its graph lies below or on the graph.
-
B.
isQuadrangleOf
Indicates that one entity is a four-sided polygon (quadrilateral) that has the other entity as its defining instance or member.
-
C.
isRectangular
Indicates that an object or shape has the properties of a rectangle, typically with four sides and right angles between adjacent sides.
-
D.
isNondegenerate
Indicates that the object or structure has no trivial, collapsed, or singular cases and thus satisfies the required non-degeneracy conditions.
-
E.
hasLinesThroughEachPoint
Indicates that for every point in the relevant space or set, there exists at least one line that passes through that point.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f42b11251881908070b93355de64ad |
completed | May 1, 2026, 4:24 a.m. |
Created at: April 18, 2026, 4:50 a.m.