Triple
T5766731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LHC Run 1 |
E127233
|
entity |
| Predicate | heavyIonSpecies |
P66268
|
FINISHED |
| Object | lead–lead collisions |
—
|
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: lead–lead collisions | Statement: [LHC Run 1, heavyIonSpecies, lead–lead collisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heavyIonSpecies Context triple: [LHC Run 1, heavyIonSpecies, lead–lead collisions]
-
A.
typeOfIsotopesProduced
Indicates the kinds or categories of isotopes that are generated or produced by a given process, source, or entity.
-
B.
isotopes
Indicates that two or more atomic nuclei are variants of the same chemical element that differ in neutron number (and thus mass number) but share the same number of protons.
-
C.
isTransuranic
Indicates that an element has an atomic number greater than that of uranium, placing it beyond uranium in the periodic table.
-
D.
isHighlyRadioactive
Indicates that the subject emits ionizing radiation at a very high level relative to typical or safe standards.
-
E.
mostAbundantIsotope
Indicates that one isotope of an element is identified as the most frequently occurring (highest natural abundance) among all its isotopes.
- F. None of above. chosen
Provenance (4 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02ac9603481909e3fa295d7904a15 |
completed | March 22, 2026, 5:45 p.m. |
Created at: March 22, 2026, 3:49 p.m.