Triple
T10315167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psychrolutidae |
E241995
|
entity |
| Predicate | vernacularNameUsage |
P80396
|
FINISHED |
| Object | "blobfish" often refers to members of this family |
—
|
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: "blobfish" often refers to members of this family | Statement: [Psychrolutidae, vernacularNameUsage, "blobfish" often refers to members of this family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vernacularNameUsage Context triple: [Psychrolutidae, vernacularNameUsage, "blobfish" often refers to members of this family]
-
A.
vernacularNameAppliedTo
chosen
Indicates that a particular common or vernacular name is assigned or applied to an entity.
-
B.
vernacularGroup
Indicates a relationship where entities are grouped or associated based on sharing the same vernacular (local or commonly spoken) language.
-
C.
multilingualName
Indicates that an entity has one or more names expressed in multiple natural languages.
-
D.
languageCommonlyCalled
Indicates that one language is commonly referred to or known by a particular alternative name or label.
-
E.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:48 a.m.