Triple
T6233007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cockcroft–Walton experiment |
E139400
|
entity |
| Predicate | reactionProduced |
P490
|
FINISHED |
| Object | alpha particle |
—
|
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: alpha particle | Statement: [Cockcroft–Walton experiment, reactionProduced, alpha particle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactionProduced Context triple: [Cockcroft–Walton experiment, reactionProduced, alpha particle]
-
A.
chemicalTypeProduced
Indicates that a process, reaction, or entity results in the production of a specific type or class of chemical.
-
B.
produces
chosen
Indicates that one entity creates, generates, or yields another entity as a result or output.
-
C.
increasesProductionOf
Indicates that one entity causes a rise or enhancement in the amount or rate at which another entity is produced.
-
D.
reaction
Indicates a chemical or physical process in which one set of substances or conditions transforms into another, often involving interaction, change, or response between entities.
-
E.
fusionReactionExample
Indicates that one entity serves as an example or instance of a specific fusion reaction involving the other entity.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062efa25c8190a54f5a6f5b5ad24f |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.