Triple
T16267786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tardigrada |
E394915
|
entity |
| Predicate | cellNumber |
P15558
|
FINISHED |
| Object | fixed cell number in many species (eutely) |
—
|
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: fixed cell number in many species (eutely) | Statement: [Tardigrada, cellNumber, fixed cell number in many species (eutely)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellNumber Context triple: [Tardigrada, cellNumber, fixed cell number in many species (eutely)]
-
A.
numberOfCells
chosen
Indicates the total count of individual cells associated with or contained in a given entity.
-
B.
cellLevels
Indicates a relationship where specific levels or layers within a cell (or cellular structure) are identified, characterized, or associated with another entity.
-
C.
numberOfCellBlocks
Indicates the total count of distinct cell blocks associated with or contained within a given entity.
-
D.
cellType
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
E.
cellTypeUsed
Indicates that a particular type of cell is employed or utilized in relation to another entity or process.
- 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_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. |
Created at: April 10, 2026, 5:05 a.m.