Triple
T31577628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malapterurus |
E805737
|
entity |
| Predicate | electricDischargeType |
P21522
|
FINISHED |
| Object | strong, low-frequency pulses |
—
|
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: strong, low-frequency pulses | Statement: [Malapterurus, electricDischargeType, strong, low-frequency pulses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricDischargeType Context triple: [Malapterurus, electricDischargeType, strong, low-frequency pulses]
-
A.
electricDischargeFunction
Indicates a relationship where one entity serves to produce, control, or facilitate the release of electric charge from another entity.
-
B.
typeOfElectricity
chosen
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
C.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
D.
usesElectricOrganDischarges
Indicates that an entity produces and utilizes electric organ discharges, typically for functions such as communication, navigation, or predation.
-
E.
isElectrically
Indicates that one entity has an electrical property, connection, or interaction in relation to 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 30, 2026, 10:22 p.m.