Triple
T26254513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janko group J4 |
E656681
|
entity |
| Predicate | isExampleIn |
P41975
|
FINISHED |
| Object | sporadic group theory |
—
|
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: sporadic group theory | Statement: [Janko group J4, isExampleIn, sporadic group theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExampleIn Context triple: [Janko group J4, isExampleIn, sporadic group theory]
-
A.
hasExample
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
B.
usedAsExampleIn
chosen
Indicates that one entity is cited or presented as an illustrative example within another entity, such as a text, discussion, or explanation.
-
C.
isCanonicalExampleOf
Indicates that something serves as a standard or typical instance that exemplifies a concept, category, or pattern.
-
D.
includesExamplesSuchAs
Indicates that one entity provides specific instances or samples that illustrate or clarify another entity.
-
E.
hasExampleType
Indicates that something is associated with a specific type or category of example that characterizes or illustrates it.
- F. None of above.
Provenance (3 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcd2e688190b54e36b0ff0d9187 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:08 p.m.