Triple
T28740150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euglenida |
E731213
|
entity |
| Predicate | cellCoveringProperty |
P165277
|
FINISHED |
| Object | flexible and deformable |
—
|
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: flexible and deformable | Statement: [Euglenida, cellCoveringProperty, flexible and deformable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellCoveringProperty Context triple: [Euglenida, cellCoveringProperty, flexible and deformable]
-
A.
cellCovering
chosen
Indicates that one entity forms a covering or enclosing layer around a cell or group of cells.
-
B.
hasCoveringRadius
Indicates the maximum distance from any point in a space to the nearest point in a given set, defining how well that set covers the space.
-
C.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
D.
edgeCoverage
Indicates that one element (such as a test, path, or configuration) covers or exercises a specific edge or connection in a graph or network structure.
-
E.
fieldCovered
Indicates that a specified field or area is physically or functionally covered by some material, object, or condition.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:02 a.m.