Triple
T31576963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariopsis felis |
E805721
|
entity |
| Predicate | hasPectoralSpines |
P171982
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ariopsis felis, hasPectoralSpines, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPectoralSpines Context triple: [Ariopsis felis, hasPectoralSpines, yes]
-
A.
hasSpines
Indicates that one entity possesses or is characterized by spines or spine-like structures.
-
B.
hasDorsalRidge
Indicates that one entity possesses a raised or elongated ridge along its dorsal (back) surface in relation to another entity or context.
-
C.
hasGraspingSpinesOn
Indicates that one entity possesses grasping spines located on a specified part or surface of another entity.
-
D.
hasHingedPlastronOrCarapace
Indicates that an entity possesses a plastron or carapace that is hinged, allowing parts of the shell to move relative to each other.
-
E.
pectoralSpineCharacteristic
chosen
Indicates a specific feature, quality, or condition associated with a pectoral spine in the relationship or observation being described.
- 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_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 30, 2026, 10:22 p.m.