Triple
T17477423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remipedia |
E425574
|
entity |
| Predicate | oxygenCondition |
P31417
|
FINISHED |
| Object | low-oxygen tolerance |
—
|
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: low-oxygen tolerance | Statement: [Remipedia, oxygenCondition, low-oxygen tolerance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oxygenCondition Context triple: [Remipedia, oxygenCondition, low-oxygen tolerance]
-
A.
oxygenRequirement
chosen
Indicates the level or type of oxygen needed by an entity to live, function, or operate.
-
B.
oxygenValueApprox
Indicates that the oxygen value of an entity is approximately equal to a specified reference value, within an acceptable margin of error.
-
C.
oxygenationIndicator
Indicates that something serves as a marker or measure of the presence, level, or status of oxygenation in a system or process.
-
D.
usedSupplementaryOxygen
Indicates that an entity received or utilized additional oxygen support beyond normal atmospheric breathing, typically via medical equipment.
-
E.
oxygenPhysiology
Indicates the physiological processes, functions, or effects involving oxygen in an organism.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bd865081909b5f84405c40ff14 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.