Triple
T18485759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unh |
E451684
|
entity |
| Predicate | elementGroup |
P131855
|
FINISHED |
| Object | group 6 (via seaborgium) |
—
|
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: group 6 (via seaborgium) | Statement: [Unh, elementGroup, group 6 (via seaborgium)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elementGroup Context triple: [Unh, elementGroup, group 6 (via seaborgium)]
-
A.
labelGroup
Indicates that an entity is assigned to or associated with a particular group label used for categorization or organization.
-
B.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
-
C.
childGroup
Indicates that one group is a subordinate or contained subgroup (child) of another group (parent) within a hierarchical structure.
-
D.
allyGroup
Indicates that two or more entities belong to the same allied group or faction, cooperating or aligned in purpose or interests.
-
E.
buttonGrouping
Indicates that multiple buttons are associated together as a single logical or functional group.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d722808190a97828cae8e3846e |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:35 a.m.