Triple
T36805190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dubnium |
E909428
|
entity |
| Predicate | discoveryControversy |
P1783
|
FINISHED |
| Object | subject of naming dispute between US and Soviet teams |
—
|
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: subject of naming dispute between US and Soviet teams | Statement: [dubnium, discoveryControversy, subject of naming dispute between US and Soviet teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryControversy Context triple: [dubnium, discoveryControversy, subject of naming dispute between US and Soviet teams]
-
A.
controversyType
Indicates the specific kind or category of controversy associated with an entity or situation.
-
B.
controversy
chosen
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
C.
dataControversy
Indicates that there is dispute, concern, or disagreement surrounding the collection, use, interpretation, or ownership of certain data.
-
D.
locationOfControversy
Indicates the place or setting where a dispute, debate, or controversy occurs or is centered.
-
E.
controversialBecause
Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:12 p.m.