Triple
T31576961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariopsis felis |
E805721
|
entity |
| Predicate | barbelLocation |
P171980
|
FINISHED |
| Object | around mouth |
—
|
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: around mouth | Statement: [Ariopsis felis, barbelLocation, around mouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barbelLocation Context triple: [Ariopsis felis, barbelLocation, around mouth]
-
A.
barLocation
Indicates that one entity is the physical location or venue where a bar is situated or operates in relation to another entity.
-
B.
barbelCount
Indicates the number of barbels (whisker-like sensory organs) an entity possesses.
-
C.
barbelPresence
Indicates whether an entity possesses barbels (whisker-like sensory appendages), typically along the mouth or head.
-
D.
benchLocation
Indicates that a bench is located at or associated with a specific place or position.
-
E.
bayLocation
Indicates that an entity (such as a bay) is geographically located in or along a specified place or region.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:22 p.m.