Triple
T24806956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson solids |
E620679
|
entity |
| Predicate | areNotInfiniteFamilies |
P158116
|
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, areNotInfiniteFamilies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areNotInfiniteFamilies Context triple: [Johnson solids, areNotInfiniteFamilies, true]
-
A.
numberOfFamilies
Indicates the total count of distinct family units associated with a given entity or context.
-
B.
possibleLargerFamily
Indicates that one entity could belong to a larger family group that includes or extends beyond another entity’s family.
-
C.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
D.
isMonofamilial
Indicates that something involves or is designed for a single family unit, rather than multiple families.
-
E.
hasNotableCardFamily
Indicates that an entity is associated with a specific, distinguished group or family of related cards.
- 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_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 4:50 a.m.