Triple
T34744581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blenniiformes |
E1001599
|
entity |
| Predicate | scaleCoverage |
P181566
|
FINISHED |
| Object | reduced scales |
—
|
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: reduced scales | Statement: [Blenniiformes, scaleCoverage, reduced scales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleCoverage Context triple: [Blenniiformes, scaleCoverage, reduced scales]
-
A.
stageCoverage
Indicates that one entity provides or has coverage, representation, or support for another within a particular stage or phase of a process or workflow.
-
B.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
-
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.
segmentCovered
Indicates that one segment or portion of something is fully or partially covered or spanned by another.
-
E.
expansionCoverage
Indicates the extent to which a given expansion (such as a geographic, functional, or service-area enlargement) is applied or covered within a specified scope or domain.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.