Triple
T24600920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul trap |
E608818
|
entity |
| Predicate | typicalIonSpecies |
P156712
|
FINISHED |
| Object | Ca+ ions |
—
|
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: Ca+ ions | Statement: [Paul trap, typicalIonSpecies, Ca+ ions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIonSpecies Context triple: [Paul trap, typicalIonSpecies, Ca+ ions]
-
A.
heavyIonSpecies
Indicates that the related entity is a type or category of ion characterized by a relatively large mass or high atomic number compared to light ions.
-
B.
hasIonizationStructure
Indicates that one entity exhibits or defines the pattern, distribution, or state of ionization present in another entity.
-
C.
mostAbundantIsotope
Indicates that one isotope of an element is identified as the most frequently occurring (highest natural abundance) among all its isotopes.
-
D.
commonIsotope
Indicates that two substances share the same most naturally abundant isotope of an element.
-
E.
intendedIsotope
Indicates that one entity is the specific isotope that another entity is meant or designed to refer to, use, or produce.
- 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:30 a.m.