Triple
T18485739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unh |
E451684
|
entity |
| Predicate | basedOnElementName |
P131851
|
FINISHED |
| Object | unnilhexium |
—
|
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: unnilhexium | Statement: [Unh, basedOnElementName, unnilhexium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnElementName Context triple: [Unh, basedOnElementName, unnilhexium]
-
A.
nameElement
Indicates that one entity serves as the name or label assigned to another entity or element.
-
B.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
C.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
D.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
E.
basedOnType
Indicates that one entity is derived, determined, or classified according to the type or category of another entity.
- 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.