Triple
T6146599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H8 beam line |
E137092
|
entity |
| Predicate | hasRadiationField |
P69441
|
FINISHED |
| Object | mixed particle radiation |
—
|
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: mixed particle radiation | Statement: [H8 beam line, hasRadiationField, mixed particle radiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadiationField Context triple: [H8 beam line, hasRadiationField, mixed particle radiation]
-
A.
isHighlyRadioactive
Indicates that the subject emits ionizing radiation at a very high level relative to typical or safe standards.
-
B.
hasXRaySources
Indicates that an entity possesses or is associated with one or more X-ray emitting sources.
-
C.
radioactiveIsotopesDetected
Indicates that the presence of radioactive isotopes has been detected in or associated with the referenced entity or context.
-
D.
hasNuclearPhase
Indicates that an entity undergoes or possesses a distinct stage or period characterized by nuclear-related processes, properties, or activities.
-
E.
usedRadioisotope
Indicates that one entity employed or applied a specific radioisotope in an action, process, or context involving another entity.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cdeeaa88190948d9db6eb2dbf46 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:16 p.m.