Triple
T10639838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mormyridae |
E250691
|
entity |
| Predicate | usesElectricOrganDischargesFor |
P95117
|
FINISHED |
| Object | navigation |
—
|
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: navigation | Statement: [Mormyridae, usesElectricOrganDischargesFor, navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesElectricOrganDischargesFor Context triple: [Mormyridae, usesElectricOrganDischargesFor, navigation]
-
A.
usesElectricityFor
Indicates that one entity relies on or employs electricity as the power source to operate, perform a function, or carry out an activity for another entity or purpose.
-
B.
hasElectrode
Indicates that one entity is equipped with, contains, or is associated with an electrode component.
-
C.
electricDischargeFunction
Indicates a relationship where one entity serves to produce, control, or facilitate the release of electric charge from another entity.
-
D.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
E.
usesElectricFrequency
Indicates that one entity operates or functions by relying on a specified electric frequency provided by another entity or context.
- 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_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. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:04 p.m.