Triple
T1095878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isotope Separator On-Line Device |
E24269
|
entity |
| Predicate | supportsExperimentType |
P2119
|
FINISHED |
| Object | beta-decay spectroscopy |
—
|
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: beta-decay spectroscopy | Statement: [Isotope Separator On-Line Device, supportsExperimentType, beta-decay spectroscopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsExperimentType Context triple: [Isotope Separator On-Line Device, supportsExperimentType, beta-decay spectroscopy]
-
A.
hasTypeOfExperiment
chosen
Indicates that an experiment is associated with or classified under a specific type or category of experiment.
-
B.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
C.
supportsMissionType
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
-
D.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
E.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99ffb3481908cd168b6c58e1c6d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.