Triple
T18485758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unh |
E451684
|
entity |
| Predicate | elementBlock |
P57059
|
FINISHED |
| Object | d-block (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: d-block (via seaborgium) | Statement: [Unh, elementBlock, d-block (via seaborgium)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elementBlock Context triple: [Unh, elementBlock, d-block (via seaborgium)]
-
A.
blockType
chosen
Indicates that one entity is classified as a specific type or category of block in relation to another entity.
-
B.
componentElement
Indicates that one entity is a constituent or part of another, larger entity or structure.
-
C.
stageElement
Indicates that one entity functions as a component or part within the structure or configuration of another entity.
-
D.
relatedBlock
Indicates that one block is associated with or connected to another block in some relevant way.
-
E.
interactiveElement
Indicates that one entity functions as an interface component designed to receive and respond to user actions initiated by 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_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. |
Created at: April 10, 2026, 11:35 a.m.