Triple
T13589346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bq |
E324650
|
entity |
| Predicate | quantityKind |
P20230
|
FINISHED |
| Object | activity (of a radionuclide) |
—
|
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: activity (of a radionuclide) | Statement: [Bq, quantityKind, activity (of a radionuclide)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quantityKind Context triple: [Bq, quantityKind, activity (of a radionuclide)]
-
A.
quantityType
Indicates that one entity is the type or category of quantity to which another entity (a specific measured or measurable amount) belongs.
-
B.
quantitySymbol
Indicates that a particular symbol is used to represent a given quantity in a mathematical, scientific, or formal context.
-
C.
usesQuantity
Indicates that one entity employs or applies a specified amount or measure of another entity in performing an action or fulfilling a function.
-
D.
typeOfMeasure
Indicates that one entity specifies the kind or category of measurement used to quantify or evaluate another entity.
-
E.
quantificationType
chosen
Indicates the specific kind or category of quantity or measurement being applied in a given context.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb055cc98819091fab597b69e5e3e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.