Triple
T2390451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lawrencium |
E48928
|
entity |
| Predicate | isPostTransitionMetalLike |
P38149
|
FINISHED |
| Object | true (predicted) |
—
|
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: true (predicted) | Statement: [lawrencium, isPostTransitionMetalLike, true (predicted)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPostTransitionMetalLike Context triple: [lawrencium, isPostTransitionMetalLike, true (predicted)]
-
A.
metallicity
Indicates the proportion of an object's mass that is made up of elements heavier than hydrogen and helium, typically used to describe the chemical richness of stars or galaxies.
-
B.
isTransuranic
Indicates that an element has an atomic number greater than that of uranium, placing it beyond uranium in the periodic table.
-
C.
stateMetal
Indicates that an entity is in a metallic state or exhibits properties characteristic of a metal.
-
D.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
E.
hasLuster
Indicates that one entity possesses a shiny, glossy, or reflective surface quality.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc87457388190822d5506327db8f2 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc682d094819081a96ffb77c4c42a |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:57 p.m.