Triple
T23321722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Ernst Claus |
E591167
|
entity |
| Predicate | rutheniumDiscoveryYear |
P3836
|
FINISHED |
| Object | 1844 |
—
|
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: 1844 | Statement: [Karl Ernst Claus, rutheniumDiscoveryYear, 1844]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rutheniumDiscoveryYear Context triple: [Karl Ernst Claus, rutheniumDiscoveryYear, 1844]
-
A.
discoveryOfNickel
Indicates the event or relationship in which nickel is first identified, found, or recognized as a distinct substance or element.
-
B.
wereFirstRealizedExperimentallyInYear
Indicates the year in which something was first successfully demonstrated or confirmed through experimental observation or testing.
-
C.
discoveredBy
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
D.
discoveryDate
chosen
Indicates the date on which something was first discovered or identified.
-
E.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978672148190bb90804361bb896b |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.