Triple
T16312715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nihonium |
E396096
|
entity |
| Predicate | IUPACGroupName |
P122643
|
FINISHED |
| Object | boron group (group 13) |
—
|
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: boron group (group 13) | Statement: [nihonium, IUPACGroupName, boron group (group 13)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IUPACGroupName Context triple: [nihonium, IUPACGroupName, boron group (group 13)]
-
A.
IUPACName
Indicates the standardized chemical name assigned to a substance according to IUPAC nomenclature rules.
-
B.
IUPACSymbolFor
Indicates that one entity is the official IUPAC-approved symbol or abbreviation that denotes the other entity.
-
C.
hasChemicalClass
Indicates that an entity belongs to, or is categorized under, a particular chemical class based on its structural or compositional characteristics.
-
D.
exampleCompoundName
Indicates that something serves as an illustrative or representative compound name used for demonstration or example purposes.
-
E.
commonCompoundNameElement
Indicates that two chemical compound names share a common structural or naming element within their nomenclature.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288dc30f48190b508220429b66e92 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.