Triple
T36805186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dubnium |
E909428
|
entity |
| Predicate | predictedChemicalBehavior |
P186556
|
FINISHED |
| Object | similar to tantalum |
—
|
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: similar to tantalum | Statement: [dubnium, predictedChemicalBehavior, similar to tantalum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predictedChemicalBehavior Context triple: [dubnium, predictedChemicalBehavior, similar to tantalum]
-
A.
hasChemicalProperty
Indicates that an entity possesses or exhibits a specific chemical property or characteristic.
-
B.
keyChemicalDiscussed
Indicates that a particular chemical substance is a central topic of discussion in a given context or communication.
-
C.
predictedEffect
Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
-
D.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
E.
hasChemicalClass
Indicates that an entity belongs to, or is categorized under, a particular chemical class based on its structural or compositional characteristics.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:12 p.m.