Triple
T10639837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mormyridae |
E250691
|
entity |
| Predicate | electricOrganDischargeType |
P75588
|
FINISHED |
| Object | weak |
—
|
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: weak | Statement: [Mormyridae, electricOrganDischargeType, weak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricOrganDischargeType Context triple: [Mormyridae, electricOrganDischargeType, weak]
-
A.
electricDischargeFunction
Indicates a relationship where one entity serves to produce, control, or facilitate the release of electric charge from another entity.
-
B.
electrodeType
Indicates the specific kind or classification of an electrode associated with an entity or used in a given context.
-
C.
hasElectrode
Indicates that one entity is equipped with, contains, or is associated with an electrode component.
-
D.
hasNumberOfElectrodes
Indicates the relationship that specifies how many electrodes are associated with a given entity.
-
E.
firingCharacteristic
chosen
Indicates the specific way in which an entity initiates or sustains firing or discharge, such as its pattern, mode, or conditions of activation.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfcbe5308190986bba438d19e852 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:04 p.m.