Triple
T31648660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venefica |
E807656
|
entity |
| Predicate | hasCommonNameForFamily |
P61588
|
FINISHED |
| Object | duckbill eels |
—
|
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: duckbill eels | Statement: [Venefica, hasCommonNameForFamily, duckbill eels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonNameForFamily Context triple: [Venefica, hasCommonNameForFamily, duckbill eels]
-
A.
belongsToFamilyCommonName
chosen
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
B.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
C.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
D.
namedForFamily
Indicates that one entity is named in honor of, or derived from the name of, a particular family or family group.
-
E.
hasFamilyNameInGroupName
Indicates that a group’s name includes or is derived from the family name of a person associated with that group.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0303622ce08190b359c9d247268729 |
completed | May 12, 2026, 10:39 a.m. |
| PD | Predicate disambiguation | batch_6a03030c02fc81908e546dba291b1240 |
completed | May 12, 2026, 10:38 a.m. |
Created at: April 30, 2026, 10:52 p.m.