Triple
T31643753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradoxoglanis |
E807527
|
entity |
| Predicate | electricOrgan |
P95116
|
FINISHED |
| Object | present |
—
|
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: present | Statement: [Paradoxoglanis, electricOrgan, present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricOrgan Context triple: [Paradoxoglanis, electricOrgan, present]
-
A.
usesElectricOrganDischargesFor
Indicates that an entity employs electric organ discharges as a means to affect, interact with, or communicate with another entity or target.
-
B.
usesElectricOrganDischarges
chosen
Indicates that an entity produces and utilizes electric organ discharges, typically for functions such as communication, navigation, or predation.
-
C.
isSoundProducedBy
Indicates that a particular sound is generated or emitted by a specified source or entity.
-
D.
usesElectricGuitar
Indicates that an entity performs, creates, or is associated with an action or role that involves playing or employing an electric guitar.
-
E.
featuresElectricPiano
Indicates that something includes or makes use of an electric piano as a notable element or component.
- 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_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 30, 2026, 10:50 p.m.