Triple
T28740113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euglenida |
E731213
|
entity |
| Predicate | cellCovering |
P165277
|
FINISHED |
| Object | flexible pellicle |
—
|
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 pellicle | Statement: [Euglenida, cellCovering, flexible pellicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellCovering Context triple: [Euglenida, cellCovering, flexible pellicle]
-
A.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
B.
networkCoverage
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
-
C.
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.
-
D.
fieldCovered
Indicates that a specified field or area is physically or functionally covered by some material, object, or condition.
-
E.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657b2b1808190a9f7c80eef2efa99 |
completed | May 2, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 6:02 a.m.