Triple
T32940440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pterophyllum scalare |
E842649
|
entity |
| Predicate | finVariation |
P175424
|
FINISHED |
| Object | many cultivated color morphs |
—
|
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: many cultivated color morphs | Statement: [Pterophyllum scalare, finVariation, many cultivated color morphs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finVariation Context triple: [Pterophyllum scalare, finVariation, many cultivated color morphs]
-
A.
flowVariation
Indicates how the rate or pattern of flow (such as water, traffic, or data) changes over time or across different conditions.
-
B.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
C.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
-
D.
variesOver
Indicates that the value, state, or behavior of one entity changes as a function of another entity or parameter.
-
E.
varies
Indicates that the value, state, or condition of one entity changes in response to differences in another entity or context.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:20 a.m.