Triple
T37291351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPAS1 |
E925672
|
entity |
| Predicate | degradedUnderCondition |
P14242
|
FINISHED |
| Object | normoxia |
—
|
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: normoxia | Statement: [EPAS1, degradedUnderCondition, normoxia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: degradedUnderCondition Context triple: [EPAS1, degradedUnderCondition, normoxia]
-
A.
usedCondition
Indicates that one entity is employed or applied under a particular state, requirement, or circumstance defined by another entity.
-
B.
partlyDowngradedTo
Indicates that an entity has been reduced in status, quality, or level to another entity, but only to a limited or partial extent rather than a full downgrade.
-
C.
degradationMechanism
Indicates the process or mechanism by which something deteriorates, breaks down, or loses its original quality or function over time.
-
D.
mayBeDowngradedTo
Indicates that one entity has the potential or permission to be reduced in status, level, or classification to another entity.
-
E.
breaksDownWhen
chosen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.