Triple
T28828335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homestake Mine, South Dakota |
E727972
|
entity |
| Predicate | experimentStart |
P67354
|
FINISHED |
| Object | late 1960s |
—
|
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: late 1960s | Statement: [Homestake Mine, South Dakota, experimentStart, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experimentStart Context triple: [Homestake Mine, South Dakota, experimentStart, late 1960s]
-
A.
experimentProgramStart
chosen
Indicates the point in time or event at which an experiment program is initiated or begins execution.
-
B.
experimentNumber
Indicates the specific identifying number assigned to an experiment within a set of experiments.
-
C.
experiment
Indicates that an entity conducts, participates in, or is the subject of a controlled test or trial to observe outcomes or validate hypotheses.
-
D.
trialServiceStart
Indicates the point in time when a trial service or trial period for a service begins.
-
E.
parallelExperiment
Indicates that one experiment is conducted alongside another under comparable conditions, typically for simultaneous testing or comparison.
- 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_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:36 a.m.