Triple
T16267750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tardigrada |
E394915
|
entity |
| Predicate | hasCryptobiosis |
P122445
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tardigrada, hasCryptobiosis, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCryptobiosis Context triple: [Tardigrada, hasCryptobiosis, true]
-
A.
biota
Indicates the presence or composition of living organisms (flora, fauna, or other life forms) associated with a given entity or environment.
-
B.
isExtremophile
Indicates that an organism thrives in environmental conditions that are extreme or hostile for most other forms of life.
-
C.
hasBiosphere
Indicates that an entity possesses or supports a biosphere, i.e., a region where living organisms and ecological processes exist.
-
D.
hasLivingSpecies
Indicates that an entity currently contains, supports, or is associated with one or more species that are alive or extant.
-
E.
describedAsLivingFossil
Indicates that something is characterized as a "living fossil," meaning it closely resembles ancient forms and has changed very little over evolutionary time.
- F. None of above. chosen
Provenance (4 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c963ec8190b059fecac6248cd9 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.