Triple
T28828290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homestake experiment |
E727970
|
entity |
| Predicate | tankContent |
P124266
|
FINISHED |
| Object | perchloroethylene cleaning fluid |
—
|
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: perchloroethylene cleaning fluid | Statement: [Homestake experiment, tankContent, perchloroethylene cleaning fluid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tankContent Context triple: [Homestake experiment, tankContent, perchloroethylene cleaning fluid]
-
A.
mainTankCapacity
Indicates the maximum volume of fuel or liquid that the primary tank is designed to hold.
-
B.
hasTank
Indicates that an entity possesses, is equipped with, or contains a tank (such as a storage tank, fuel tank, or similar vessel).
-
C.
mainTankName
Indicates that the subject entity has the specified name as its primary or main tank designation.
-
D.
cargoContents
chosen
Indicates that one entity contains or carries another entity as its cargo.
-
E.
fuelTankConfiguration
Indicates how a system’s fuel tanks are arranged, connected, or structured relative to one another.
- 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_69f65939b9c481909b9ca8035227862b |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:36 a.m.