Triple
T36468738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Möbius transformation |
E898486
|
entity |
| Predicate | formsGroupUnder |
P193575
|
FINISHED |
| Object | composition |
—
|
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: composition | Statement: [Möbius transformation, formsGroupUnder, composition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsGroupUnder Context triple: [Möbius transformation, formsGroupUnder, composition]
-
A.
formedGroup
Indicates that multiple entities have come together to create or establish a group or collective unit.
-
B.
formedAsGroupOf
Indicates that something came into existence by being created or organized as a collection of multiple members acting together as a group.
-
C.
allyGroup
Indicates that two or more entities belong to the same allied group or faction, cooperating or aligned in purpose or interests.
-
D.
groupFormedPartOf
Indicates that a group was formed as a constituent or subset of a larger group or organization.
-
E.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: May 3, 2026, 4:10 p.m.