Triple
T28828256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homestake experiment |
E727970
|
entity |
| Predicate | usedTargetIsotope |
P36680
|
FINISHED |
| Object | chlorine-37 |
—
|
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: chlorine-37 | Statement: [Homestake experiment, usedTargetIsotope, chlorine-37]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTargetIsotope Context triple: [Homestake experiment, usedTargetIsotope, chlorine-37]
-
A.
intendedIsotope
Indicates that one entity is the specific isotope that another entity is meant or designed to refer to, use, or produce.
-
B.
usedTargetMass
Indicates that an action or process utilized a specific mass or quantity of a target entity.
-
C.
commonIsotope
Indicates that two substances share the same most naturally abundant isotope of an element.
-
D.
usedRadioisotope
chosen
Indicates that one entity employed or applied a specific radioisotope in an action, process, or context involving another entity.
-
E.
isLighterIsotopeOf
Indicates that one isotope has a lower atomic mass (fewer neutrons) than another isotope of the same element.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 6:36 a.m.