Triple
T35270102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolly Varden |
E1018639
|
entity |
| Predicate | hasFinFeature |
P201057
|
FINISHED |
| Object | adipose fin typical of salmonids |
—
|
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: adipose fin typical of salmonids | Statement: [Dolly Varden, hasFinFeature, adipose fin typical of salmonids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinFeature Context triple: [Dolly Varden, hasFinFeature, adipose fin typical of salmonids]
-
A.
hasBankCharacteristic
Indicates that a bank possesses a particular attribute, feature, or quality.
-
B.
hasFrontFeature
Indicates that an entity possesses a specific characteristic, component, or attribute located on its front side.
-
C.
hasFinancialFunction
Indicates that an entity performs, supports, or is responsible for a specific financial role, operation, or service in relation to another entity.
-
D.
hasSideFeature
Indicates that an entity possesses a specific secondary or auxiliary feature on its side or lateral aspect.
-
E.
hasFeatureOnBanknotes
Indicates that a particular feature, such as a design element or security mark, appears on one or more banknotes.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69ffc515e4b08190810b2a29b2885162 |
completed | May 9, 2026, 11:36 p.m. |
Created at: May 3, 2026, 4:02 p.m.