Triple
T29992685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BASE collaboration |
E761921
|
entity |
| Predicate | conductsExperimentAt |
P1591
|
FINISHED |
| Object | Antiproton Decelerator at CERN |
—
|
NE NERFINISHED |
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: Antiproton Decelerator at CERN | Statement: [BASE collaboration, conductsExperimentAt, Antiproton Decelerator at CERN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conductsExperimentAt Context triple: [BASE collaboration, conductsExperimentAt, Antiproton Decelerator at CERN]
-
A.
conductedExperimentsIn
Indicates that an entity performed or carried out experiments within a specified location or context.
-
B.
experimentedOn
Indicates that one entity conducted experiments or tests on another entity as the subject of investigation.
-
C.
carriedExperiment
Indicates that an entity performed, conducted, or executed a particular experiment.
-
D.
parallelExperiment
Indicates that one experiment is conducted alongside another under comparable conditions, typically for simultaneous testing or comparison.
-
E.
hostsExperiment
chosen
Indicates that one entity provides the environment or infrastructure in which another entity’s experiment is conducted or run.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791c8e088190a0766badc1d3b5cd |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:39 p.m.