Triple
T33212137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REXIS |
E850188
|
entity |
| Predicate | elementSensitivity |
P24994
|
FINISHED |
| Object | magnesium |
—
|
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: magnesium | Statement: [REXIS, elementSensitivity, magnesium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elementSensitivity Context triple: [REXIS, elementSensitivity, magnesium]
-
A.
sensitivityFeature
chosen
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
-
B.
hasSensibility
Indicates that an entity possesses awareness, responsiveness, or sensitivity to stimuli or experiences.
-
C.
sensitivityRegion
Indicates the specific area or domain within which a subject is particularly responsive, vulnerable, or reactive to a given influence or condition.
-
D.
isSurfaceSensitive
Indicates that the property, behavior, or measurement depends strongly on the characteristics or condition of a surface rather than the bulk material.
-
E.
sensoryModality
Indicates the type of sensory channel (e.g., visual, auditory, tactile) through which an experience, perception, or information is received or processed.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.