Triple
T7188710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sievert |
E167632
|
entity |
| Predicate | conversionFromRem |
P31138
|
FINISHED |
| Object | 1 Sv = 100 rem |
—
|
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: 1 Sv = 100 rem | Statement: [sievert, conversionFromRem, 1 Sv = 100 rem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionFromRem Context triple: [sievert, conversionFromRem, 1 Sv = 100 rem]
-
A.
conversionUse
Indicates that one entity is used as a means, method, or context for converting another entity from one form, state, or representation to another.
-
B.
convertedUnit
chosen
Indicates that one unit is the result of converting a quantity expressed in another unit.
-
C.
convertedFrom
Indicates that one entity has been transformed or changed in form, type, or representation from another entity.
-
D.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
E.
convertsTo
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e3d9188190ba2792098d76fb86 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.